Safari Web Extension Packager upload section missing in App Store Connect — prerequisites?

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:

  1. Sign in to App Store Connect as the Account Holder of an active Apple Developer Program membership.
  2. Open an existing app, then select Xcode Cloud.
  3. 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, ZIP upload control, or button to start packaging. I also checked another app under the same team and saw the same introduction page.

Additional details:

  • My existing Safari extension was previously distributed as an iOS app using an Xcode project. I want to use the web-based Packager for its next update while retaining the existing app identity.
  • The extension source is a WXT project and the Safari ZIP has already been generated. I have not reached any upload or build-validation step, because the upload UI is missing.
  • During my September 6 checks, the Developer Program agreement and App Store Connect agreements were accepted, with no pending agreement prompt.
  • I contacted Apple Developer Support. The account-support team said they could not diagnose this technical issue and directed me to the Developer Forums.

Could an Apple engineer clarify:

  1. Is Safari Web Extension Packager currently available to all eligible developer teams, or is access still being rolled out? Are there any country/region restrictions, including mainland China?
  2. What exact prerequisites control whether the upload section appears? Is enabling a conventional Xcode Cloud workflow from a local Xcode project required first, even when the intended input is only a web extension ZIP?
  3. Can the Packager update an existing app previously built with Xcode, or does the initial Packager setup require a new app record?
  4. What is the correct App Store Connect page or navigation path for a team that only sees the Xcode Cloud introduction?

I am asking about access to the web-based packaging UI, rather than how to convert an extension into a local Xcode project. A documented activation step or confirmation of the availability requirements would be very helpful.

Thank you.

Screenshot: the Xcode Cloud page shows only the introduction and Open Xcode button, with no Packager upload section.

Safari Web Extension Packager upload section missing in App Store Connect — prerequisites?
 
 
Q