Post not yet marked as solved
Click to stop watching this thread.
You have stopped watching this post. Click to start watching again.
contentPostList.repliesup-voted.tooltip
Replied In
Need help troubleshooting Universal Links
Thanks for the reply, Musashi.I appreciate the information, but a different experiment has provided some additional context. Here's what happened: I updated my device to iOS 13 (in beta) and updated my xCode to 11 beta 5. Sure enough, the same project files builds and deploys via xCode and now the Universal links work when I click on them in a Slack window. No other changes were made to the xCode project.I have admitted confounded the situation by attempting this on a different version of xCode. However, this does appear to confirm that my AASA is staged correctly. I also went back and confirmed that the previous build did not work (by restoring it via TestFlight.) Unfortunately, neither the xCode 11 beta 5 or the TestFlight installation vector do not appear to induce any of the swcd messages discussed in our previous messages. You can see an afternoon of testing here, filtered by the swcd process: https://pastebin.com/9uFTUrLEEither the format of the domain authorization messages has completely changed, I am not filtering the log messages properly, or something else has gone wrong. (Bear in mind that I was able to get my test URL to trigger successfully from Slack and launch my app.)At present, things "work" with the following caveats:1. The app I'm testing has a feature for opening links, but when I open my own Universal links from within my app, Safari is opened instead of hitting my callback (in the same app). Why is that? Am I doing something wrong here? How can I get Universal links to be... universal?2. The Universal links work on iPad, but not iPhone. I am going to continue trying to get this working on both device types.Again, thanks for your reply. If you or anyone can comment on the two issues outlined above, I would appreciate it.