Hi structankit, Did you figure out the solution? I made a mistake in one of my reply, it is NOT fixed for me on Safari 14610.1.26 either, still need to manually grant.

Hi bweinstein, From the MDN, the event will be trigger when installed or upgraded. Yes, I have created the feedback 8695776 - https://feedbackassistant.apple.com/feedback/8695776 Thank you

Thanks bweinstein, the feedback is created https://feedbackassistant.apple.com/feedback/8978683

It is related to using shared UserDefaults among different targets. To do that, I need to set both the AppExtension and WebExtension to the same app group. Unfortunately, my AppExtension doesn't have app group before, after I set the AppExtension to an app group ("my-app-extension", same as the suiteName in getting UserDefaults), The AppExtension can't get the previous storages. Looks it is impossible to resolve the issue.

Thanks bweinstein, that's sounds a plan. Actually, I tried the FileManager.default, if I can copy files across different targets, e.g, copying the AppExt's UserDefaults file my-app-extension.plist to file:///Users/username/Library/Containers/WebExt bundle identifier/Data/Library/Preferences, problem is solved. But seems FileManager.default can only operate file in current process files.

Just to be more detailed, when I migrating to WebExt, I didn't remove the AppExt bundle in my app. So the app have both AppExt and WebExt, and WebExt has the SFSafariAppExtensionBundleIdentifiersToReplace key to replace the AppExt. I was hoping the app can be compatible with both Safari 12/13 and Safari 14+. Is this a valid practice? Thank you very much

Found the solution, this API will resolve: https://developer.apple.com/documentation/safariservices/sfsafariapplication/2202266-showpreferencesforextension.

+1, though Testflight supports MacOS now, it would be better if we can just sign and install Safari webext locally. Safari WebExt is not a typical MacOS app, it is closely coupled with browser. It seems none of the popular test automation framework has the privilege to config the Mac privacy settings and "allow unsigned extension" in Safari developers settings Compared with for Chromium, Firefox, the test automation is straightforward, this limitation brings a lot of difficulties to the e2e testing.