Custom URL Protocol Missing After macOS Upgrade

I have an application that upon installation, registers a custom URL protocol (scheme) like foo:// using the lsregister command line tool.

Recently I noticed that the custom URL protocol is missing after an upgrade of macOS (Catalina to Big Sur). It appears that the upgrade de-registers the custom URL protocol while my application is still installed as it was before the macOS upgrade.Yet, any application functionality depending on its custom URL protocol is broken.

The only workaround seems to reinstall my application, or at minimum re-register the custom URL protocol manually.

Is this expected behavior for macOS upgrades? Do applications need to re-register any custom URL protocol again after a macOS upgrade? Why are these not retained as one would expect?

I'd appreciate any comments or thoughts, or perhaps an explanation for this behavior. Why would an OS upgrade break such integrations between the already installed application and the OS.

I'd appreciate any comments or thoughts

I don’t have any obvious suggestions here, other than to say that if a specific system behaviour is causing you grief then you should definitely file a bug about that.

Please post your bug number, just for the record.

Share and Enjoy

Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Custom URL Protocol Missing After macOS Upgrade
 
 
Q