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: Older Pushwoosh iOS SDK builds opened URLs with the deprecated UIApplication.openURL(_:). This was changed in 6.7.7 to UIApplication.open(_:options:completionHandler:), which Apple requires. On older builds (6.5.x and earlier) deep links can work from push notifications but still fail inside an In-App message.

   • Solution: Update to the current stable Pushwoosh iOS SDK — the latest release is 7.2.0. Note that the SDK ships as the PushwooshXCFramework pod and requires an iOS deployment target of 13.0 or higher. See the Pushwoosh iOS SDK releases for the current version and upgrade notes.

2. Deep link handling code placement: The way your application handles incoming URLs may be implemented in the wrong place, particularly if your app supports scenes (UISceneDelegate).

   • Solution: Make sure 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, that is scene(_:openURLContexts:). If your app does not use scenes, the logic belongs in application(_:open:options:) in your AppDelegate. Placing it only in AppDelegate while a SceneDelegate is active can cause deep links from certain contexts, such as In-App messages, to fail.