You can set a category in Xcode under the macOS App target, in the General tab under the Identity section. That will add it to the built Info.plist for you.
Post not yet marked as solved
No, Safari does not have a Single Purpose Policy. Apple's App Store guidelines are here: https://developer.apple.com/app-store/review/guidelines/
Safari 16.4 does support "MAIN" for registerContentScripts.
Post not yet marked as solved
This indicates your service worker is throwing an exception, like using an API that Safari does not support. At this time there is no way to see that exception to debug it.
You can try making the background script use the scripts array instead of service_worker, which is still supported in v3 in Safari. That way you can debug any errors in the Develop menu.
This is a good use case that would be nice to address. Can you file feedback at Feedback Assistant?
In the meantime, you can use the browser.permission.request() API to prompt for permissions. Those will affect content script injection too.
Post not yet marked as solved
This is likely because you are converting a manifest_version 3 extension and you are on an older macOS release that shipped before version 3 was supported by Safari. You can ignore these messages from the tool and it should be testable still in Safari 15.4 or later.
Post not yet marked as solved
Yes, adding new permissions has no impact on existing users. New host permissions will need the user to allow them when the extension next tries to access tabs, cookies, pages, etc that match the new host patterns.
Post not yet marked as solved
This is not currently supported. If this is something you would like to see, please send us you use cases via Feedback Assistant. Thanks!
Post not yet marked as solved
The limit increased to 80MB in the latest iOS 15.1 beta.
Post not yet marked as solved
You need to enable Web Inspector on your device in Settings > Safari > Advnaced. Then your extension pages and popups will appear in the device submenu under the Develop menu.
Post not yet marked as solved
Safari currently requires a PNG image for icons. If you would like to see SVG supported, please send us feedback via Feedback Assistant. Thanks!
Post not yet marked as solved
Could you attach the extension source or file a feedback ticket via Feedback Assistant - https://feedbackassistant.apple.com with it attached so we can look at it? (At least the whole manifest and locale directories.)
You shouldn't need to re-enable the extension each build, just rebuilding in Xcode will reload an enabled extension in Safari.
To be clear, your extension isn't interfering with clicking, some other software on your Mac is. Sometimes this can be a screen recorder, or some other third-party application that has invisible windows over the whole screen.
Can you post a copy of the manifest you are using? Does it happen with any manifest? Does it work with Xcode 12.3 (released earlier this week)?
Post not yet marked as solved
This sounds like a bug. Can you send feedback via Feedback Assistant - https://feedbackassistant.apple.com so we can investigate? Thanks!
