Can we get the list or count of the URLs blocked using the Safari web extension content blocking on the iOS app?
Safari Extensions
RSS for tagEnhance and customize the web browsing experience on Mac, iPhone, and iPad with Safari Extensions
Posts under Safari Extensions tag
105 Posts
Sort by:
Post
Replies
Boosts
Views
Activity
In iOS 18, internal extension pages cannot navigate to external webpages, either via href links or through JS methods such as window.location.replace. Nothing happens when you try to navigate to an external webpage. Only other internal pages can be navigated to. This wasn't an issue on previous versions of iOS.
It would be appreciated if this can be fixed as soon as possible.
Feedback ID: FB14194963
The process to reproduce:
Create a new extension with Xcode 16 beta.
Run it on the simulator or any iOS device with iOS 18 beta installed.
Open Safari on your Mac, then open Develop -> Device you use.
Unable to access these menus for iOS 18:
1. Extension - Extension Background Content
2. Extension - Extension Pop-up Page - popup.html
However, for iOS 17.4, I can see these options in Develop -> Device iOS(17.4).
I have another extension on the App Store that is not working on the iOS 18 beta, but I am unable to debug it because of this issue.
I am following these instructions to created a Safari Web Extension App project:
https://developer.apple.com/documentation/safariservices/safari_web_extensions/creating_a_safari_web_extension
When I try to compile the default code, I get this error:
Circular dependency between modules 'Dispatch' and 'Foundation'
At one point, it showed the error was in generatedassetssymbols.swift file, although I cant replicate that now.
macOS, Sonoma 14.0, xcode 15.4
Anyone know what is going on? It is literally the default project without any changes.
Here is my manifest.json:
"permissions": [
"<all_urls>",
"storage",
"unlimitedStorage",
"activeTab"
]
Despite declaring "unlimitedStorage" in permissions, I encounter the following error when trying to save files exceeding approximately 3MB:
Invalid call to browser.storage.local.set(). Exceeded storage quota.
This issue did not occur in iOS 17. Is this behavior intentional or is it a bug? If it is intentional, is there an alternative method to handle large file?