We’re presently making an attempt to implement Common Hyperlinks with the intention to navigate customers between our core iOS apps however have just lately hit a brick wall that has me fairly stumped.
App 1 is an iOS app that presents a WebView based mostly dashboard to the person with content material delivered from a subdomain (eg. https://dashboard.area.com/)
When the person faucets a button from throughout the net content material within the dashboard the app makes a url request out to a different subdomain and path (eg. https://breakout.area.com/go?foo=bar)
This url is registered as a common hyperlink and may open the goal iOS app – App 2. The issue is that it finally ends up opening the system browser and makes an attempt to load the url as a substitute.
We have now an apple-app-site-association file hosted at https://breakout.area.com/.well-known/ and have accurately declared the trail and app particular info inside, in addition to registering the applinks:breakout.area.com area in App 2‘s entitlements.
Moreover we all know that our implementation and configuration is sound as we are able to reliably set off that common hyperlink url (opening App 2) via different testable means.
Nevertheless when the common hyperlink request initiator originates from App 1’s WebView talked about within the second paragraph above – iOS fails to intercept the url request and treats it as it could every other net hyperlink.
My first thought was that iOS was treating the initiator area as being the identical because the common hyperlink area.
Nevertheless Apple documentation right here would point out that utilizing subdomains ought to fulfill the rule the place the community request should not originate from throughout the identical area because the common hyperlink with the intention to set off the interception and open the goal app.
So to check this we modified the button on the dashboard to name to a brand new common hyperlink working out of a unique prime stage area (eg. https://breakout.new-domain.com/go?foo=bar) and whaddya know – it labored. App 2 opened up efficiently.
So I suppose my query is, has anyone else come throughout this explicit challenge earlier than? I’m very eager to know of a workaround (if one exists) that does not require us to make use of a novel prime stage area simply to serve the performance of a common hyperlink between App 1 and App 2.