The Missing Call: Why application(...continue userActivity...) Isn't Triggering in iOS 13
Problem: You've implemented Universal Links in your iOS app and are expecting the application(_:continue userActivity:restorationHandler:) method to be called when a user clicks on a link on another device. However, in iOS 13 and later, this method is mysteriously silent, leaving you with a broken workflow.
Understanding the Issue:
In iOS 13, Apple introduced changes to how Universal Links are handled, potentially leading to the application(_:continue userActivity:restorationHandler:) method not being called. This can be frustrating because it disrupts the seamless integration of your app with other devices and platforms.
Scenario:
Let's imagine you're building a social media app where users can share content through Universal Links. You've implemented the following code:
func application(_ application: UIApplication, continue userActivity: NSUserActivity, restorationHandler: @escaping ([UIUserActivityRestoring]?) -> Void) -> Bool {
if userActivity.activityType == NSUserActivityTypeBrowsingWeb {
if let incomingURL = userActivity.webpageURL {
// Handle the shared content from the incoming URL
print("Received URL: \(incomingURL)")
}
return true
}
return false
}
This code snippet attempts to capture the URL from a shared link and process it within the app. However, in iOS 13 and later, the application(_:continue userActivity:restorationHandler:) method is not called, leaving your app unable to handle the incoming URL.
Insights:
- The Silent Killer: The lack of a clear explanation from Apple can make debugging this issue quite challenging.
- iOS 13 & Beyond: The behavior you're experiencing is linked to changes introduced in iOS 13 regarding Universal Link handling.
- Alternative Solutions: Fortunately, there are alternative approaches you can use to manage this scenario effectively.
Solutions:
application(_:open:options:): Theapplication(_:open:options:)method offers a reliable alternative for handling Universal Links. This method will be called regardless of iOS version, providing a more consistent solution.
func application(_ app: UIApplication, open url: URL, options: [UIApplication.OpenURLOptionsKey : Any] = [:]) -> Bool {
if url.scheme == "your-app-scheme" {
// Handle the shared content from the incoming URL
print("Received URL: \(url)")
return true
}
return false
}
application(_:open:sourceApplication:annotation:): For cases where you need information about the source app that initiated the Universal Link, theapplication(_:open:sourceApplication:annotation:)method can provide valuable context.
func application(_ application: UIApplication, open url: URL, sourceApplication: String?, annotation: Any) -> Bool {
if url.scheme == "your-app-scheme" {
// Handle the shared content from the incoming URL
print("Received URL: \(url)")
print("Source Application: \(sourceApplication ?? "Unknown")")
return true
}
return false
}
Additional Value:
By leveraging these alternatives, you can ensure your app continues to function correctly with Universal Links across all iOS versions. Remember to implement proper error handling and logging to gain insights into any issues that might arise during the transition.
Resources:
- Apple Developer Documentation - Universal Links
- Stack Overflow - Universal Links Not Working in iOS 13
Conclusion:
While the application(_:continue userActivity:restorationHandler:) method might not be the ideal solution for Universal Links in iOS 13 and later, there are robust alternatives readily available. By adapting your code and utilizing these solutions, you can continue to provide a seamless and user-friendly experience for your app, regardless of the iOS version your users are running.
