Скачать или смотреть How to Postpone the Initialization of AVPlayer in SwiftUI

Learn how to effectively manage AVPlayer initialization in SwiftUI, enabling dynamic audio playback within your application.
---
This video is based on the question https://stackoverflow.com/q/67976166/ asked by the user 'it75' ( https://stackoverflow.com/u/15396505/ ) and on the answer https://stackoverflow.com/a/67976437/ provided by the user 'jnpdx' ( https://stackoverflow.com/u/560942/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: Postpone init() AVPlayer SwitUI

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Managing AVPlayer Initialization in SwiftUI

Working with audio playback in SwiftUI can pose various challenges, especially when you want to control how and when your AVPlayer gets initialized. One question that developers often ask is how to postpone the initialization of AVPlayer to allow for more dynamic control, particularly when dealing with user inputs. In this guide, we will explore an effective solution to this problem by refactoring our existing code.

The Problem

In a typical SwiftUI application, when you create an instance of an object that conforms to ObservableObject, such as AudioPlayerAV, you often initialize it directly in the view’s init. However, this becomes tricky if you want to initialize the player with a URL or path that may not be readily available during the init phase. The core issue is that you cannot make an @ ObservedObject or @ StateObject optional, which limits your flexibility in controlling when the player gets set up.

The Solution: Refactoring for Flexibility

To solve this problem, we need to refactor the AudioPlayerAV class so that its initialization logic is separated from the loading of audio content. Here’s how we can do that.

Step 1: Modify the AudioPlayerAV Class

We will start by updating AudioPlayerAV to include a method for initializing the player with a URL rather than doing it in the constructor. This allows us to create a method named loadPlayer, which we can call whenever we need to set up the player.

Updated Code Snippet

[[See Video to Reveal this Text or Code Snippet]]

Step 2: Implement the Dynamic Loading in ContentView

Now that we have modified the AudioPlayerAV class, we can use it in our ContentView while also allowing for dynamic user input. This is done by using a TextField to accept a URL input from the user which will then be used to initialize the player.

Updated ContentView Code

[[See Video to Reveal this Text or Code Snippet]]

Conclusion

By refactoring your AudioPlayerAV class and managing the loading process through a dedicated method, you can effectively postpone the initialization of your AVPlayer until the necessary data is available. This method enhances your application's flexibility and improves user experience by allowing dynamic playback capabilities.

Now you can manage audio playback in SwiftUI far more effectively, giving you greater control over when and how your audio files are played. Happy coding!