Post

Replies

Boosts

Views

Activity

Reply to Unable to access logs artifact from Web Extension Packager
I’m experiencing exactly the same issue. I have already tested: Both Manifest V2 and Manifest V3 A completely minimal extension with no JavaScript, permissions, host permissions, APIs, or external dependencies A newly created App Store Connect app and Bundle ID Multiple version and build numbers Both App Store Distribution and Development Distribution fail during export with the same message requesting the logs artifact. However, the Web Extension Packager build page provides no Logs, Artifacts, or Download button. Because a clean minimal extension and a completely new app fail identically, this appears to be a Web Extension Packager/Xcode Cloud signing or export issue rather than an extension-code issue. Could an Apple engineer please confirm how to access the underlying export logs or investigate the affected Packager builds?
Topic: Safari & Web SubTopic: General Tags:
Sep ’26
Reply to Unable to access logs artifact from Web Extension Packager
I’m experiencing exactly the same issue. I have already tested: Both Manifest V2 and Manifest V3 A completely minimal extension with no JavaScript, permissions, host permissions, APIs, or external dependencies A newly created App Store Connect app and Bundle ID Multiple version and build numbers Both App Store Distribution and Development Distribution fail during export with the same message requesting the logs artifact. However, the Web Extension Packager build page provides no Logs, Artifacts, or Download button. Because a clean minimal extension and a completely new app fail identically, this appears to be a Web Extension Packager/Xcode Cloud signing or export issue rather than an extension-code issue. Could an Apple engineer please confirm how to access the underlying export logs or investigate the affected Packager builds?
Topic: Safari & Web SubTopic: General Tags:
Replies
Boosts
Views
Activity
Sep ’26