Let's say I have a web application that calls my own application through a custom URL scheme, and after the native application has completed its work, it returns to my web application by opening the callback URL.
Everything works fine when my web application runs in Safari. But what happens if the user saves the web application on the main screen (by creating a "Web clip")? In this case, it starts in a separate process from a regular safari and has separate cookies and cache.
Therefore, when the native application tries to return to the web application, the URL is supposedly opened by Safari, not the web clip, and the session will be lost. (And not just the session - the whole state of the page, which in a rich Javascript-based web application can be a lot of things with non-trivial launch time.)
Is this assumption correct? And if so, is there any way around it? Is there a way to make iOS try to open the URL using a web clip if one is installed?
source share