Скачать или смотреть Solving the Firebase DeepLink Issues on Killed/Terminated App States for iOS 14

Discover how to effectively manage `Firebase DeepLink` problems when your iOS app is in a Killed/Terminated state with our comprehensive guide.
---
This video is based on the question https://stackoverflow.com/q/65929749/ asked by the user 'eNeF' ( https://stackoverflow.com/u/3266278/ ) and on the answer https://stackoverflow.com/a/66152222/ provided by the user 'eNeF' ( https://stackoverflow.com/u/3266278/ ) 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: Firebase DeepLink does not work on Killed/Terminated App state in iOS14

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.
---
Understanding Firebase DeepLink Issues on iOS 14

When integrating Firebase DeepLinking, developers may encounter issues, especially when the app is in a Killed or Terminated state. A common problem is that even if the app opens upon clicking a deep link, it fails to trigger the necessary methods to retrieve data from the link. This can be frustrating and challenging to diagnose, particularly with the peculiarities of iOS 14’s app lifecycle.

The Problem

In iOS 14, when the app is not running (in a Killed or Terminated state), various delegate methods responsible for handling deep links do not receive the required data to process the links. Here's a breakdown of the core issues:

didFinishLaunchingWithOptions: This method’s launchOptions parameter is always nil, leading to missed deep link data.

openURL:options: and continue userActivity:restorationHandler:: Both these methods fail to trigger when opening the app from a terminated state.

As a result, even though the app launches, it lacks the context needed to handle deep links effectively, leaving developers searching for solutions.

An Effective Solution: Migrating to SceneDelegate

After experimenting with various workarounds, the most effective solution for addressing these challenges involves migrating to Apple's new App Structure using SceneDelegate. This new structure allows for better handling of deep links, especially when the app is in a non-active state.

Step-by-Step Migration Process

Here’s a comprehensive approach to implement the SceneDelegate in your app for better deep link handling:

1. Configure SceneDelegate

You need to capture incoming deep links in the SceneDelegate methods. Below is a sample implementation:

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

2. Handle User Activities and URLs

To manage user activities and open URL contexts, implement these additional methods in the SceneDelegate:

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

3. Configure Info.plist

Finally, it’s crucial to set up your Info.plist correctly to reflect the new scene management. Make sure your configuration looks somewhat like this:

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

Conclusion

Migrating to the SceneDelegate configuration not only modernizes your app but also resolves critical issues tied to deep linking when your app is in a non-active state, particularly on iOS 14. By following the outlined steps, developers can ensure they are capturing deep link data effectively, thereby enhancing the user experience.

If you have further questions or need assistance with implementation, feel free to reach out!