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?