Thank you for your suggestion. That idea did cross our minds, but it is not easy to implement. The responsible JS code that makes use of the fonts is delivered by 3rd party. Thats what makes it difficult to transition to WKWebView and also to maintain the list of fonts as part of our app as it can change without us knowing. A second reason against this solution is the increase of application size as some fonts have 10MB. Thats why I am first trying to figure out whether there is an option to supress the popups and make it behave as WKWebView in this regard.

@C_Wiz. I did send the feedback on 10th of June 2022. So far no reaction from Apple. I suggest you to fill a feedback as well. More feedbacks means better chance of getting any reaction/fix.

I have an update on this topic. It seems the deep links continue to work if you use NSWorkspace.shared.open() but they do not work when you try to open them in Terminal via open <url> This used to work in older macOS versions.

Thank you for the reply, I have filled FB10807608 describing the compatibility issue. Our app uses Apple Installer instead of SMAppService as we support systems all the way back to El Capitan. So I will not create a ticket for that as I would not be able to provide sample code. Kind regards, Jakub

Hello, I would also be very much interested in what this means and also to what this message refers to. In our installer, we are using: JS code in Ditribution.xml to perform some OS compatibility checks Postinstall scripts to load our services Installer plugins with custom UI flows for the installer Any insight would be appreciated.