So try to launch the app from another domain. Probably safari wont care to check whether the destination url is a universal link, when the link is into the same domain that user is on. From what I have seen, launching the app from the same domain mostly fails. If this works, you may have been trying to launch the app from the same domain as the link. If the app still don't get launched after the step a., try mailing the link to a webmail such as gmail and open the webmail site in safari and try clicking the link.
This time on, the app should get launched because tapping the banner should have saved the preference to open the link in app.ī. Tap the banner to open the app, close the app by pressing home button, get back to safari and try launching the app by tapping the link again. A banner should appear that can open your app. Try pulling down on the safari page that opened when the link was clicked like the way you 'pull to refresh'. In Safari, If the Context Menu shows "Open in " in safari, but tapping the link opens the link in safari itself instead of launching the app,Ī. If the link is not launching the app, try The link will turn yellow and tapping on the link should open your app, and not Safari. Open Notes app, type the link you expect to open the app. You should see a "Open in " in the Context Menu. Tap and hold on the link that you expect to launch the app. Quick steps to check whether you have implemented Universal Link correctly. I'm personally very curious about how Universal Links work and what edge cases exist. Let me know if you discover what the issue is. However, /b/* should be unaffected and still open your app directly. If you do that, subsequent visits to /a/* will open in browser, not app. So if you have separate routes, /a/* and /b/*, if you click /a/* and it opens your app directly, you then have the option in the top right corner of the app to click through to /a/*. Note that clicking through to the site => disabling UL seems path specific, based on the paths you specify in the apple-app-site-assocation file. Then in Safari, you can pull down to reveal a banner at the top of the page with "Open". Note that if a Universal Link succeeds in opening your app and then you click through to Safari (by tapping your site in the top right corner of the nav bar in app), then iOS stops opening the app when you visit that URL. Others have reported that clicking links in Google search results have opened the app directly. Clicking from other apps (iMessage, Mail, Slack, etc.) has worked. In my personal testing, clicking/typing in a link in Safari has never once opened the app directly. Error message pulled from here, quick (incomplete) instructions on using CloudFlare for TLS here.
The error message will look like Sep 21 14:27:01 Derricks-iPhone swcd : 02:27:01.878907 PM # Rejecting URL '' for auth method 'NSURLAuthenticationMethodServerTrust': -6754/0xFFFFE59E kAuthenticationErr. It's buried in the OS logs, not application logs.
IOS logs an error message in the system logs if you don't have TLS set up properly on the domain specified in your entitlements. Try pasting your domain into this link validator and make sure there are no issues: (credit to ShortStuffSushi - see repo)