Why isn't the deep link in my In-App message working when tapped on iOS devices, even though it works elsewhere (like Push Notifications)?

If a deep link (e.g., yourappscheme://path/to/content) within an In-App message isn't opening the correct screen or functioning as expected specifically on iOS devices, there are two common causes:

1. Outdated iOS SDK: Your application might be using an older version of the Pushwoosh iOS SDK. Newer versions of iOS handle URL opening differently. Our SDK was updated (versions 6.7.7+) to align with Apple's latest requirements (using UIApplication.open(_:options:completionHandler:) instead of the deprecated UIApplication.openURL(_:)). Using an older SDK (like 6.5.x or earlier) can lead to issues where deep links work from Push Notifications but fail within the context of an In-App message.

   • Solution: Update your application to use the latest stable version of the Pushwoosh iOS SDK. Check the Pushwoosh iOS SDK release notes for the latest version and integration guides.

2. Deep Link Handling Code Placement: The way your application handles incoming URLs might be implemented in a location less suitable for modern iOS development, particularly if your app supports scenes (UISceneDelegate).

   • Solution: Ensure your deep link handling logic (the code that processes the incoming URL and navigates the user) is implemented in the appropriate delegate method. For apps using UISceneDelegate, the relevant method is typically scene(_:openURLContexts:). If your app does not use scenes, the logic would be in application(_:open:options:) within your AppDelegate. Placing this logic incorrectly (e.g., solely in AppDelegate when SceneDelegate is active) can cause deep links from certain contexts, like In-App messages, to fail. Consult the iOS SDK integration documentation for the correct implementation based on your app's structure.