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!
Post not yet marked as solved
You can do the conversion on Catalina with Xcode 12.2 or later and Safari 14 installed. I suggest watching Meet Safari Web Extensions - https://developer.apple.com/videos/play/wwdc2020/10665/.
Post not yet marked as solved
You also need to make sure you enable Allow Unsigned Extensions in the Develop menu when you are using local built extension apps.
You need to pass an extension folder to the tool, not a zip file. Just expand the zip file first.
Post not yet marked as solved
This actually could be done with a content script that sets window.location.href to a new URL.
Safari Web Extensions have a per-site permission model and the existing permissions do not transfer from your Safari App Extension.
Post not yet marked as solved
This is likely due to the match patterns for file and ftp. Safari does not support extensions for those schemes, so the matches array will appear empty after those unsupported patterns are filtered out.
