White flash when opening a new tab overridden by a Safari Web Extension on iOS Safari intermittently displays a white flash when opening a new tab overridden by a web extension. I reproduced this on an iPhone 13 mini running iOS 26.5 using a minimal test extension. Minimal reproduction The extension replaces the new tab page through chrome_url_overrides.newtab. The page has a static magenta background, set directly on the root element and through inline CSS. The test page contains no JavaScript, images, fonts, external stylesheets or network requests. Steps to reproduce Install and enable a Safari Web Extension that overrides the new tab page with a static magenta HTML page. Select the extension for new tabs in Safari settings. Open Safari in normal browsing mode. Open a new tab and wait for the magenta page to appear. Open another new tab. Repeat several times. Expected: The page area remains magenta throughout the transition. Actual: The page area intermittently transitions from magenta → white → magenta. The issue reproduces without JavaScript or external resources, so the flash does not require delayed script execution or image loading. Is this a known issue with Safari’s handling of new tab overrides? Is there a supported way for an extension to control the background displayed during this transition?

Hello, I'm trying to package a Safari Web Extension using Apple's web-based Safari Web Extension Packager in App Store Connect. However, both export processes consistently fail, and I have been unable to determine the root cause. Environment Apple Developer Program membership: Active App Store Connect app configured for both iOS and macOS Development environment: Windows PC and iPad; no access to a Mac Packaging method: Safari Web Extension Packager in App Store Connect Issue Every packaging attempt results in these two errors: Development Distribution: Exporting for Development Distribution failed. Please download the logs artifact for more information. App Store Distribution: Exporting for App Store Distribution failed. Please download the logs artifact for more information. The interface does not appear to provide any button or link to download the referenced logs artifact. As a result, I cannot access the diagnostic information needed to investigate the failure. Troubleshooting performed To determine whether the problem was caused by my extension's code, I created and uploaded a separate, minimal test extension. The same export failures occur with the minimal test extension, not just my original extension. Questions How can I download the logs artifact referenced in the error message? Could this be a server-side packaging, signing, or provisioning issue in App Store Connect? I have already reviewed Apple's documentation, but it does not provide enough information to diagnose these specific failures. Any guidance from someone who has successfully used the current web-based packaging workflow, or from an Apple engineer familiar with this service, would be appreciated. Thank you.

Hello, I am trying to package and distribute a Safari Web Extension using the web-based Safari Web Extension Packager in App Store Connect. My Apple Developer Program membership is active, and I have already completed the following: Created an explicit Bundle ID. Created an iOS app record in App Store Connect named Kuzey SGK. The app is currently in Prepare for Submission status. I can access the app's Xcode Cloud tab. I can also access Users and Access > Xcode Cloud. According to Apple's documentation: “After creating an app record, navigate to the Xcode Cloud tab. Under Safari Web Extension Packager, click Upload.” However, there is no “Safari Web Extension Packager” section at all under the Xcode Cloud tab for my app. The page only displays the standard Xcode Cloud information and “Get started in Xcode.” I am using App Store Connect from Windows in a web browser. My understanding from Apple's Safari Web Extension documentation is that the web-based packager should allow packaging an existing web extension without requiring a Mac or Xcode. I have not configured a standard Xcode Cloud workflow or connected a source repository, because the Safari Web Extension Packager documentation does not list those steps as prerequisites. Apple Developer Program Support reviewed my request and referred me to the Developer Forums because this appears to be a technical issue. My support case number is 102956602442. Could someone please clarify: Is there an additional step required to enable the Safari Web Extension Packager for a newly created developer account or app? Is a standard Xcode Cloud workflow required before the Packager becomes visible? Is the Packager currently available to all Apple Developer Program members? Thank you.

I am trying to use Safari Web Extension Packager to upload a web extension ZIP through App Store Connect, following this documentation: https://developer.apple.com/documentation/safariservices/packaging-and-distributing-safari-web-extensions-with-app-store-connect However, I cannot find the Packager upload section at all. Steps to reproduce: Sign in to App Store Connect as the Account Holder of an active Apple Developer Program membership. Open an existing app, then select Xcode Cloud. Scroll to the bottom of the page. Actual result: The page only shows the standard Xcode Cloud introduction, with “Get started in Xcode” and an “Open Xcode” button. There is no Safari Web Extension Packager section or ZIP upload control. Another app under the same team shows the same introduction page. Additional details: The existing Safari extension was previously distributed as an iOS app using Xcode. I want to use the Packager for the next update while retaining the existing app identity. The source is a WXT project and the Safari ZIP has been generated. I cannot reach the upload or build-validation step. During my September 6 checks, the Developer Program and App Store Connect agreements were accepted, with no pending agreement prompt. Apple Developer Support's account-support team directed me to the Developer Forums because they could not diagnose this technical issue. Could an Apple engineer clarify: Is Packager available to all eligible teams, or still being rolled out? Are there country/region restrictions, including mainland China? What prerequisites control the upload section? Must a team first enable a conventional Xcode Cloud workflow through local Xcode, even if the intended input is only a web extension ZIP? Can Packager update an existing app previously built with Xcode, or does initial setup require a new app record? What is the correct page or navigation path when only the Xcode Cloud introduction is visible? This question concerns access to the web-based packaging UI. A documented activation step or confirmation of availability requirements would be helpful. Screenshot of the missing upload section:

I’m packaging a Safari Web Extension using the web-based Safari Web Extension Packager in App Store Connect. The ZIP uploads successfully, the manifest is accepted, and the Packager automatically creates the related Extension identifier. However, every build fails during export with: Exporting for App Store Distribution failed. Please download the logs artifact for more information. It also shows: Exporting for Development Distribution failed. Please download the logs artifact for more information. There is no Logs, Artifacts, or Download button on the build or issue page. To isolate the problem, I tested: Manifest V2 and Manifest V3 A minimal extension containing only HTML and icons No JavaScript, permissions, host permissions, APIs, or external dependencies A completely new App Store Connect app A new explicit Bundle ID A name-matched extension ZIP Multiple version and build numbers Every test produced exactly the same export errors. The App Store Connect agreement is active, and the Account Holder has access to cloud-managed distribution certificates. Because even a clean minimal extension and a newly created app fail identically, this appears to happen during cloud signing, provisioning, or archive export—not while parsing the extension. Questions: How can I download the logs artifact requested by the error when the Packager interface does not provide it? Can Apple confirm whether the web-based Packager currently has an export or automatic-signing issue? Is there any required certificate, provisioning profile, App ID configuration, or account permission that the Packager does not create automatically?

Hi! I currently have a web extension sucessfully published to Firefox. And now I'm trying to make the same web extension available for Safari. Here's a link to the source code for this extension: https://code.on.nilsnh.no/nilsnh/rolodex Steps to reproduce: Through appstoreconnect I create a new app. Within the app I select the tab Xcode Cloud, and scroll down to the Safari Web Extension Packager. When I try to upload a .zip file of my extension I get the error message: "NetworkError when attempting to fetch resource." According to the docs this upload feature should be compatible with any browser. I'm using Firefox version 154 running on Linux Mint 22.3. I've filed an issue for this last month. Support have said that they'll keep me updated but so far there's been little or no progress.

Instead of rejecting the extension with a reasonable, polite error, Safari on Tahoe crashes when the manifest.json file is properly formatted for Firefox instead of Chrome. ------------------------------------- Translated Report (Full Report Below) ------------------------------------- Process: Safari [88741] Path: /Volumes/VOLUME/*/Safari.app/Contents/MacOS/Safari Identifier: com.apple.Safari Version: 26.4 (21624.1.16.11.4) Build Info: Safari-7624001016011004~1 Code Type: X86-64 (Native) Role: Background Parent Process: launchd [1] Coalition: com.apple.Safari [97627] User ID: 503 Date/Time: 2026-07-19 21:54:12.9042 -0700 Launch Time: 2026-07-18 10:38:48.3440 -0700 Hardware Model: MacBookPro16,2 OS Version: macOS 26.4.1 (25E253) Release Type: User Bridge OS Version: 10.4 (23P4242) Crash Reporter Key: E10AFED8-44D7-B68A-A06B-6237E159410E Incident Identifier: 0E512E91-4C4E-4D10-9518-6F0757C5E943 Sleep/Wake UUID: 5396E9EB-E238-4D56-BE08-D966DCE12528 Time Awake Since Boot: 580000 seconds Time Since Wake: 12175 seconds System Integrity Protection: enabled Triggered by Thread: 0, Dispatch Queue: com.apple.main-thread Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Subtype: UNKNOWN_0xD at 0x0000000000000000 Exception Codes: 0x000000000000000d, 0x0000000000000000 Termination Reason: Namespace SIGNAL, Code 11, Segmentation fault: 11 Terminating Process: exc handler [88741] VM Region Info: 0 is not in any region. Bytes before following region: 4311683072 REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL UNUSED SPACE AT START ---> __TEXT 100ff1000-100ff2000 [ 4K] r-x/r-x SM=COW /System/Volumes/Preboot/Cryptexes/App/System/Applications/Safari.app/Contents/MacOS/Safari Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 libunwind.dylib 0x7ff821b974b0 _Unwind_RaiseException + 240 1 libc++abi.dylib 0x7ff811ba5db4 __cxa_throw + 61 2 libobjc.A.dylib 0x7ff8117b8131 objc_exception_throw + 317 3 CoreFoundation 0x7ff811c832b7 -[__NSDictionaryM setObject:forKeyedSubscript:] + 1215 4 SafariSharedUI 0x7ffa19bdc6b5 -[WBSSafariExtensionStateObserver _addNamesForExtension:toMap:] + 205 5 SafariSharedUI 0x7ffa19bdc22d -[WBSSafariExtensionStateObserver _handleExtensionWasAdded:] + 208 6 CoreFoundation 0x7ff811cb1434 __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 137 7 CoreFoundation 0x7ff811d388da ___CFXRegistrationPost_block_invoke + 88 8 CoreFoundation 0x7ff811d3882d _CFXRegistrationPost + 540 9 CoreFoundation 0x7ff811c8131c _CFXNotificationPost + 769 10 Foundation 0x7ff812ed3cd1 -[NSNotificationCenter postNotificationName:object:userInfo:] + 82 11 SafariSharedUI 0x7ffa19b769b8 -[WBSExtensionsController _loadExtensions:skipEqualityCheck:] + 2505 12 SafariSharedUI 0x7ffa19b74ec7 __59-[WBSExtensionsController loadSuitableDiscoveredExtensions]_block_invoke + 62 13 SafariSharedUI 0x7ffa19b74da0 -[WBSExtensionsController loadSuitableDiscoveredExtensions] + 133 14 SafariSharedUI 0x7ffa19c5cdd2 -[WBSWebExtensionsController loadSuitableDiscoveredExtensions] + 46 15 SafariSharedUI 0x7ffa19b7490f -[WBSExtensionsController _beginMatchingExtensionsWithAttributesCompletedWithMatchingExtensions:] + 537 16 SafariSharedUI 0x7ffa19b7460f -[WBSExtensionsController _extensionDiscoveryHasNewResults:] + 331 17 libdispatch.dylib 0x7ff811a47616 _dispatch_call_block_and_release + 12 18 libdispatch.dylib 0x7ff811a5d8b2 _dispatch_client_callout + 6 19 libdispatch.dylib 0x7ff811a78679 _dispatch_main_queue_drain.cold.6 + 842 20 libdispatch.dylib 0x7ff811a53dc4 _dispatch_main_queue_drain + 107 21 libdispatch.dylib 0x7ff811a53d4b _dispatch_main_queue_callback_4CF + 31 22 CoreFoundation 0x7ff811cf66b3 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 9 23 CoreFoundation 0x7ff811cbb15c __CFRunLoopRun + 2382 24 CoreFoundation 0x7ff811d828b7 _CFRunLoopRunSpecificWithOptions + 496 25 HIToolbox 0x7ff81e9f1b8b RunCurrentEventLoopInMode + 283 26 HIToolbox 0x7ff81e9f4c4d ReceiveNextEventCommon + 599 27 HIToolbox 0x7ff81eb7d0ba _BlockUntilNextEventMatchingListInMode + 37 28 AppKit 0x7ff816236d34 _DPSBlockUntilNextEventMatchingListInMode + 172 29 AppKit 0x7ff815b2c9d5 _DPSNextEvent + 800 30 AppKit 0x7ff8167dab53 -[NSApplication(NSEventRouting) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1265 31 AppKit 0x7ff8167da629 -[NSApplication(NSEventRouting) nextEventMatchingMask:untilDate:inMode:dequeue:] + 67 32 Safari 0x7ff927853839 -[BrowserApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 214 33 AppKit 0x7ff815b1d868 -[NSApplication run] + 472 34 AppKit 0x7ff815af34cd NSApplicationMain + 800 35 Safari 0x7ff92783fac1 SafariMain + 529 36 dyld 0x7ff81182abb8 start + 3240 Thread 1:: com.apple.NSEventThread 0 libsystem_kernel.dylib 0x7ff811bbcb4e mach_msg2_trap + 10 1 libsystem_kernel.dylib 0x7ff811bcaf49 mach_msg2_internal + 83 2 libsystem_kernel.dylib 0x7ff811bc3b64 mach_msg_overwrite + 586 3 libsystem_kernel.dylib 0x7ff811bbce54 mach_msg + 19 4 CoreFoundation 0x7ff811cbc2bf __CFRunLoopServiceMachPort + 145 5 CoreFoundation 0x7ff811cbad58 __CFRunLoopRun + 1354 6 CoreFoundation 0x7ff811d828b7 _CFRunLoopRunSpecificWithOptions + 496 7 AppKit 0x7ff815c7e6a0 _NSEventThread + 158 8 libsystem_pthread.dylib 0x7ff811c00d49 _pthread_start + 115 9 libsystem_pthread.dylib 0x7ff811bfc82f thread_start + 15 ...

Hi! It seems like in Safari, elements inserted into a page by web extensions (such as and elements) are currently subject to the page's Content Security Policy. If the CSP is strict enough, this prevents these elements from loading. Based on my testing, I've found that this behavior is different in other browsers, where a page's CSP is not applied to elements inserted by an extension. Is this expected behavior in Safari, or might it be considered a bug? Any advice on working around these restrictions, as it currently prevents my extension from working correctly on websites with a strict CSP?

Is there an MDM solution that will give a Safari extension all the permissions it needs with no interaction from the end user?

Hello, We have a Network extension transparent proxy (NETransparentProxyProvider) that receives browser TCP flows as NEAppProxyTCPFlow. For each flow we create an NWConnection to the flow's original destination and set NEParameters.preferNoProxies = true - expecting the outbound connection to bypass the user's HTTP/HTTPS proxy and PAC so it goes to the destination server directly. However, in practice we see connections still being redirected to local proxy after being evaluated against the PAC rules using the destination IP and port. Our questions are: Could we expect preferNoProxies to be respected when a PAC exist on the endpoint and supersede the PAC rule decision? If yes, what would be the best way to file a bug and what information do you need? If not, is there any other way of making sure that the outbound NWConnection created by the transparent proxy is not redirected to a proxy and goes directly to the destination? One other way of avoiding our NWConnection being redirected to the proxy is to use hostname instead of destination IP. Would there be a reliable way of getting hostname for the NEAppProxyTCPFlow so that PAC can correctly filter all NWConnection based on rules? We have explored remoteHostname but it's generally not available for connections from browsers other than Safari.