macOS: Doesn't always register as latest/greatest.
Opened this issue · 0 comments
On macOS, specifically with the safe browser, registering a custom protocol works, but it's not guaranteed to open the registering app for that URI. It seems that with different app versions installed, or moved to different parts of the OS (through app translocation, eg), it's currently not guaranteed that a registered URI will open the registering app...
I'm not sure how OSX determines what to open (version... location... something else...). And I'm not sure if there's something on the app level that ought to/could be done to avoid this.
eg:
~/Applications/safe-browser.app opens, and registers itself to handle safe-auth://, BUT ~/downloads.safe-browser.app also exists so maybe OSX decides to open that for safe-auth:// urls, even though we just registered the former as the new handler. :(