My macOS app, AnimacX, cannot complete Developer ID distribution export in Xcode Cloud. The affected build is 1144, and the preceding build 1143 contains the following certificate lookup and creation failures. Environment: Team ID: SWWMY4BCX7 Bundle ID: app.anix.AnimacX Xcode version recorded in the Build 1143 logs: 27.1 (27A9275) Automatic signing enabled Failing step: Export archive for developer-id distribution xcodebuild -exportArchive exits with code 70 The provisioning log shows this sequence: Xcode Cloud queries certificates with type DEVELOPER_ID_APPLICATION_MANAGED. The response contains an empty data array and a total count of 0. Xcode then attempts to create a managed Developer ID Application certificate. The creation request fails with: HTTP 409 code: ENTITY_ERROR resultCode: 7460 You already have a current Developer ID Application Managed certificate or a pending certificate request.The export subsequently reports: No signing certificate "Developer ID Application" found No "Developer ID Application" signing certificate matching team ID "SWWMY4BCX7" with a private key was found. No profiles for 'app.anix.AnimacX' were found.However, the Certificates page for this team lists two Developer ID Application Managed (Xcode Cloud) certificates, both created by Xcode Cloud and expiring on February 2, 2027. I have an Admin role on the team. This workflow was working normally until recently, and I have not created, revoked, or otherwise modified any certificates. Building and uploading the macOS app to App Store Connect directly from local Xcode still succeeds. The iOS and tvOS builds and distribution workflows also continue to work normally. The failure is limited to Developer ID distribution export for macOS in Xcode Cloud. I contacted Apple Developer Support under case 103008194927 and was directed to post here. Screenshots are attached, and I can provide the full distribution logs. Could an Apple engineer help determine why Xcode Cloud returns no certificates while the creation service reports an existing certificate or pending request? What action is required to restore Developer ID export, and does this require investigation of the team’s cloud-managed signing state?

Does Xcode 27 or TestFlight support installing a watch-only beta on an Apple Watch For Your Kids device? I want to test my watch only standalone app on my kids apple watch as that is the only device I have. Is it possible to use that watch for testing standalone apple watch application. The watch is setup as kids watch on my iphone.

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.

Heyo everyone! Since Xcode 27 (27.0, 27.1, and 27.2 RC), I have not been able to export builds to the App Store through Xcode Cloud that have app-usage on the com.apple.developer.user-fonts key in the entitlements file. For some inexplicable reason, it seems as though Xcode Cloud's automatic signing is trying to map to the Font Enumeration capability instead of the other Fonts capability? Since I don't have this, it fails. However, I can archive and export these builds to App Store just fine on my local device using 27.1. Here is what Xcode Cloud's logs are spitting back: error: exportArchive Automatic signing cannot update bundle identifier “XXX”. Automatic signing cannot update your registered bundle identifier to enable Font Enumeration. Update your bundle identifier on https://developer.apple.com/account and then try again. And ideas or am I alone on this island?

Hi folks, I've been having this issue for the last few months, where Xcode Cloud fails to resolve Swift package dependencies while compiling my builds, seemingly at random. Some of my Xcode Cloud builds will fail after several minutes, with an error log looking like that : xcodebuild: error: Could not resolve package dependencies: failed downloading 'https://dl.google.com/firebase/ios/bin/grpc/1.62.2/rc0/grpcpp.zip' which is required by binary target 'grpcpp': downloadError("The request timed out.") Whenever this happens, I have to manually restart an Xcode Cloud build process (or several builds, since the error can happen multiple times in a row), to the point it's becoming increasingly painful to rely on Xcode Cloud for my workflow. The failing packages are mostly random (meaning, it's not always the same one that Xcode fails to resolve), but they are always publicly accessible, even though I have an environment variable set in my Xcode workflows to retrieve a single Github private dependency (maybe this has some kind of importance). Could anyone tell me if this is an isolated issue, or if I could do anything on my end to resolve this ? Thank you !

I'm trying to start using Xcode Cloud from a project, but the only thing I get is the message saying "Failed to create workflow" with the actual error being "Could not find item. Domain: XcodeCloudKit.XcodeCloudCommandHandler.CommandHandlerError Code: 5". Initially, it did lead me to configuring permissions on GitHub. But it failed in the end probably because the git remote of the project was pointing to another organisation, that transferred the ownership to me. I switched remote to my org, but it didn't help. So, I revoked the permission and deleted Xcode Cloud app from my GitHub in hopes that the config process would start again. It does not. All I get is this senseless error. Is Xcode Cloud functionality functioning at all in Xcode beta 27 for anyone?

Hi, Overview I am using Xcode Cloud for my multi platform app. The macOS test case fails, however the iOS test case runs and succeeds. I don't have any UI test cases written, the test case are simple and have nothing platform (macOS) specific. Questions What can I do to fix this? Is there any user privileges needed to launch the macOS app for testing? I ask because when I ran the UI tests locally it launched the app and asked for my macOS user password. Just wondering if that is the reason it didn't launch in Xcode Cloud. Error: <Appname> encountered an error (Failed to install or launch the test runner. If you believe this error represents a bug, please attach the result bundle at /Volumes/workspace/resultbundle.xcresult.(Underlying Error: Could not launch "AppnameTests. The LaunchServices launcher has returned an error. Please check the system logs for the underlying cause of the error. (Underlying Error: The operation couldn't be completed. Launch failed. (Underlying Error: Launch job spawn failed) ))) × Could not launch "<Appname>" × Could not launch "AppnameTests" × AppnameUITests.testExample() Failed to get launch progress for <XCUIApplicationImpl: 0x600000564630 <BundleID> at /Volumes/workspace/TestProducts/Debug-Dev/<Appname>.app>: Could not launch "app name". The LaunchServices launcher has returned an error. Please check the system logs for the underlying cause of the error. (Underlying Error: The operation couldn't be completed. Launch failed. (Underlying Error: Launch job spawn failed)) AppnameUITests.swift:28 * AppnameUITests.testLaunchPerformance) Failed to get launch progress for «XCUIApplicationimpl: 0x60000054630 <BundleID> at /Volumes/workspace/TestProducts/Debug-Dev/<Appname>.apps: Could not launch "<Appname>". The LaunchServices launcher has returned an error. Please check the system logs for the underlying cause of the error. (Underlying Error: The operation couldn't be completed. Launch failed. (Underlying Error: Launch job spawn failed)) AppnameUITests.swift:37 g * AppnameUITestsLaunchTests.testLaunch) Failed to get launch progress for «XCUIApplicationimpl: 0x60000054630 <BundleID> at /Volumes/workspace/Testroducts/Debug-Dev/<Appname>.apps: Could not launch "<Appname>". The LaunchServices launcher has returned an error. Please check the system logs for the underlying cause of the error. (Underlying Error: The operation couldn't be completed. Launch failed.

I am seeing Xcode Cloud reuse and reassign a single ciProduct when onboarding multiple iOS app targets from one Xcode project. Each target has its own bundle ID, PBXNativeTarget, product reference, and shared scheme. Environment: Xcode 26.6 (17F113) macOS Tahoe 26.5.2 GitHub repository connected to Xcode Cloud Project: pilot-ios/Airtap.xcodeproj Targets / shared schemes: PocketPilot.ai DEV1 — ai.airtap.dev1 PocketPilot.ai DEV2 — ai.airtap.dev2 PocketPilot.ai DEV3 — ai.airtap.dev3 PocketPilot.ai DEV4 — ai.airtap.dev4 PocketPilot.ai QA1 — ai.airtap.qa1 PocketPilot.ai QA3 — ai.airtap.qa3 Every entry above is a separate PBXNativeTarget with a distinct productReference. Each shared scheme is stored under Airtap.xcodeproj/xcshareddata/xcschemes and builds its corresponding target. QA1 and QA3 were onboarded earlier and received independent Xcode Cloud products as expected. Reproduction: In Xcode, open Xcode Cloud Reports and choose Create Workflow. Select target PocketPilot.ai DEV1 and create an archive workflow using scheme PocketPilot.ai DEV1. DEV1 appears under the correct App Store Connect app. Create another workflow for target PocketPilot.ai DEV2 using scheme PocketPilot.ai DEV2. DEV1 disappears as a separate Xcode Cloud product. Both the DEV1 and DEV2 workflows now appear under the DEV2 App Store Connect app. The App Store Connect API confirms this is not only an Xcode UI or cache issue: Before DEV2 onboarding, ciProduct F048BF00-CECF-4926-84DB-D3474CB030A9 was related to bundle ID ai.airtap.dev1. After DEV2 onboarding, that same ciProduct ID became related to bundle ID ai.airtap.dev2. The product now contains both workflows: PocketPilot DEV1 Archive / scheme PocketPilot.ai DEV1 PocketPilot DEV2 Archive / scheme PocketPilot.ai DEV2 No build was started, and both workflows are currently disabled. Expected behavior: Because every target has a different bundle ID, Xcode should create a separate Xcode Cloud product for each target, as described in the Xcode Cloud onboarding documentation. Actual behavior: The newest onboarding changes the existing ciProduct-to-App Store Connect app relationship instead of creating a new ciProduct. This moves all earlier workflows to the newest app. The public App Store Connect API cannot repair this because it supports reading and deleting ciProducts, but not creating one; ciWorkflows can only be created under an existing ciProduct. I also encountered an Xcode crash while adding another product. The crash stack included XcodeCloudNavigableItemCoordinator.removeNavigableItem(for:) and IDENavigableItemCoordinator, which may be related to the product reassignment. I can provide the crash report in Feedback Assistant if needed. A recent forum thread reports the same high-level symptom: previously created workflows migrate to the newest app. In our case, the API relationship change above makes the backend reassignment directly observable. Is this a current Xcode Cloud onboarding/backend regression? Is there a supported workaround, or can Apple Support create or restore separate ciProducts for these bundle IDs?

I’m experiencing a persistent TestFlight installation issue that started after my most recent Apple Developer Program renewal. All builds upload and process successfully in App Store Connect/TestFlight, and there are no apparent issues with the builds themselves. However, when testers try to install the apps, they receive the following error: “The requested app is not available or doesn’t exist.” Since the same problem is affecting multiple apps under the same Apple Developer account, while the builds are uploading and processing successfully, I suspect this may be related to the TestFlight/App Store Connect distribution state or account-level backend configuration after the renewal. I have already checked the builds and TestFlight configuration, but the issue still persists. Has anyone experienced the same issue after renewing their Apple Developer Program membership? If so, were you able to resolve it, and did Apple Support have to fix something on the backend? Any guidance or suggestions would be greatly appreciated.

I have a workflow where I want to specifically run some tests in the iOS 18 simulator. All while using Xcode 26 on Xcode Cloud. In my Xcode Cloud workflow I can set the iOS version, but just iOS 16, 17 and 26, but no 18? I'm very confused here Not sure which is the right channel anyway to request support to Xcode Cloud too

My project uses spm https://github.com/airbnb/lottie-spm.git. When I use xcode cloud in XCode to create a workflow, it asks me to connect airbnb in github. In fact, this repo is public, it's unnecessary. Then I tried to fork this https://github.com/airbnb/lottie-spm.git to my own domain, and xcode cloud created the workflow, but it was failed: Build - iOS encountered a failure that caused the build to fail. Issue an out-of-date resolved file was detected at /Volumes/workspace/repository/xxx.xcodeproj/project.xcworkspace/xcshareddata/swiftpm/Package.resolved, which is not allowed when automatic dependency resolution is disabled; please make sure to update the file to reflect the changes in dependencies. Running resolver because the following dependencies were added: 'lottie-spm' (https://github.com/xxx/lottie-spm.git)2026-10-04 03:11:57.970 xcodebuild[2735:14329] Writing error result bundle to /var/folders/zn/fgtz2b0j5014hc3fs53llxg80000gn/T/ResultBundle_2026-04-10_03-11-0057.xcresult Finally, I modify the spm url to original and commit, push the project, it build successfully.

Hi, Canary Mail has had approval to use the Default Mail App entitlement for years. We have a longstanding Xcode Cloud export failure involving com.apple.developer.mail-client. In our latest iOS build, compilation and archiving succeed (ARCHIVE SUCCEEDED). All three subsequent exports—App Store, Ad Hoc, and Development—fail with the same error: error: exportArchive Entitlement com.apple.developer.mail-client not found and could not be included in profile. This likely is not a valid entitlement and should be removed from your entitlements file. We checked the signing configuration and Developer portal: • The main app requests com.apple.developer.mail-client = true. • An existing manual App Store provisioning profile is active until June 2027. Decoding the downloaded profile confirms it contains com.apple.developer.mail-client = true and matches the app's bundle identifier and team. • Local development archiving also succeeds with our existing manual Default Mail App development profile. • However, Default Mail App is absent from both the Capabilities and Capability Requests tabs for this App ID. This appears related to these reports, where Apple corrected the entitlement's distribution grants: https://developer.apple.com/forums/thread/774506 https://developer.apple.com/forums/thread/800072 Our case differs because all three export modes fail, rather than only Ad Hoc. Apple's provisioning documentation describes migrating older additional entitlements into App ID managed capabilities for cloud-managed signing: https://developer.apple.com/help/account/reference/provisioning-with-managed-capabilities Could our older Default Mail App approval still be available through manual provisioning profiles but not migrated to the managed capability used by Xcode Cloud? What is the correct support route to have Apple verify/migrate this approval and ensure Development, Ad Hoc, and App Store export are supported? If the grant is already correct internally, could this be a Cloud provisioning service issue? Is there a supported way to use our approved manual App Store profile for Xcode Cloud's built-in export while this is investigated? We need to preserve default-mail functionality, so removing the entitlement is not a suitable production workaround. We can provide the full distribution logs and profile details privately to Apple Support. Thank you.

Every App Store Connect upload I sign with my Cloud Managed Apple Distribution certificate is rejected with ITMS-90035 ("Code failed to satisfy specified code requirement(s)") for the app binary and its widget extension. It happens from Xcode Cloud and from a manual Organizer upload alike. I think I have found the cause, and it looks like a Unicode normalization bug in cloud-managed signing. The certificate holder's name contains an umlaut: "Apple Distribution: Jonathan Thorsten Müller (…)". In the certificate the "ü" is precomposed (NFC, UTF-8 c3 bc). In the designated requirement that the export writes into the signature it is decomposed (NFD, "u" + U+0308, UTF-8 75 cc 88): certificate subject CN ... 4d c3 bc 6c 6c 65 72 ... ("Müller", NFC) designated requirement leaf CN ... 4d 75 cc 88 6c 6c 65 72 ... ("Müller", NFD) The bytes differ, so the signature can never satisfy its own designated requirement. It reproduces with Xcode 27.0's App template, unmodified, and without uploading anything: Archive for a generic iOS device. With no distribution identity in the local keychain, export for App Store Connect to a folder (export options: method app-store-connect, destination export, signingStyle automatic). DistributionSummary.plist shows "Cloud Managed Apple Distribution". xcodebuild -exportArchive -archivePath MyApp.xcarchive -exportPath out -exportOptionsPlist ExportOptions.plist -allowProvisioningUpdates Verify the exported app: codesign --verify --strict -vv Payload/MyApp.app Result: "valid on disk", then "does not satisfy its designated Requirement". Compare the requirement with the certificate's subject: codesign -d -r- Payload/MyApp.app codesign -d --extract-certificates Payload/MyApp.app openssl x509 -inform DER -in codesign0 -noout -subject -nameopt RFC2253,-esc_msb | xxd The same archive exported with a regular Apple Distribution certificate (same name, private key in my keychain) writes the NFC form, verifies, and App Store Connect accepts that upload. That works for manual uploads only. Xcode Cloud always signs with the cloud-managed certificate, so I cannot distribute from Xcode Cloud at all. Setup: Xcode 27.0 (27A266a) locally and in Xcode Cloud, automatic signing, one team, no custom code-signing flags. Product name, bundle IDs and file names are plain ASCII. Questions: Is this a known issue with cloud-managed signing and non-ASCII certificate names? Is there a supported way to have Xcode Cloud sign without hitting it in the meantime? If you see ITMS-90035 on Xcode Cloud and your name (or your team's) has an accent or umlaut in it, you may be hitting the same thing: run step 3 on an exported IPA and check.

Hi! I've successfully uploaded my web extension using the Web Extension Packager. However, there was a build error. When I review the list of cloud builds and click "view issues" for the failed build, I get the message: "Exporting for App Store Distribution failed. Please download the logs artifact for more information." However, I can't find any link in the app store connect web UI for viewing the logs artifact for Web Extension Packager builds.

I'm experiencing a persistent issue with Xcode Cloud where my iOS app (Spellboard) builds and archives successfully, but all three export steps fail with exit code 70: Export archive for ad-hoc distribution — exit code 70 Export archive for development distribution — exit code 70 Export archive for app-store distribution — exit code 70 Environment: Xcode Cloud Build 45, branch: main Project: Spellboard.xcodeproj Team: EinsteinAI Target: Any iOS Device (arm64) Automatic code signing (managed by Xcode Cloud) Building on a Remote Mac (additional code signing constraints) Error details from logs: The xcodebuild -exportArchive command fails during the signing phase. For example, the development distribution step shows: xcodebuild -exportArchive -archivePath /Volumes/workspace/tmp/ec4c2b30-ebd1-435f-8d8f-621326235df1.xcarchive -exportPath /Volumes/workspace/developmentexport -exportOptionsPlist /Volumes/workspace/ci/development-exportoptions.plist -DVTProvisioningIsManaged=YES -IDEDistributionLogDirectory=/Volumes/workspace/tmp/development-export-archive-logs -DVTSkipCertificateValidityCheck=YES -DVTServicesLogLevel=3 Command exited with non-zero exit-code: 70 The same pattern repeats for ad-hoc and app-store distribution exports. What I've verified: The build itself compiles successfully (all modules compile, command executed successfully) No code changes were made that would affect signing The workflow is configured with automatic signing managed by Xcode Cloud Post-action is set to TestFlight External Testing Additional constraint — Remote Mac: I'm building on a Remote Mac, which adds complexity to code signing and keychain access. The Remote Mac environment has known limitations with certificate and provisioning profile management compared to a local Mac. This may be a contributing factor to the export failures. This appears to be an issue with how Xcode Cloud is handling the Apple Distribution and Apple Development signing certificates during the export phase, not a build compilation issue. Has anyone encountered this recently, or is there a known issue with Xcode Cloud's managed signing on Remote Mac environments? Any guidance on resolving exit code 70 during the export step would be greatly appreciated.

Client error - operationID: onboardTarget, operationInput: Input(path: XcodeCloudAPI.Operations.onboardTarget.Input.Path(teamId: ""), query: XcodeCloudAPI.Operations.onboardTarget.Input.Query(), headers: XcodeCloudAPI.Operations.onboardTarget.Input.Headers(), cookies: XcodeCloudAPI.Operations.onboardTarget.Input.Cookies(), body: XcodeCloudAPI.Operations.onboardTarget.Input.Body.json(XcodeCloudAPI.Components.Schemas.TargetOnboardingRequest(projectName: "Runner", targetName: "Runner", targetType: app, repoHandle: XcodeCloudAPI.Components.Schemas.RepoHandle(host: Optional("bitbucket.org"), provider: bitbucket, repoId: ""), deviceFamilies: Optional([iPhone, iPad]), deploymentTarget: Optional("15.0"), productCreationEntryPoint: xcode_product_menu))), request: path: /teams/onboard-target, query: , method: HTTPMethod(value: OpenAPIRuntime.HTTPMethod.(unknown context at $14c94d79c).OpenAPIHTTPMethod.POST), header fields: [accept: application/json, content-type: application/json; charset=utf-8], body (prefix): { "deployment_target" : "15.0", "device_families" : [ "iPhone", "iPad" ], "product_creation_entry_point" : "xcode_product_menu", "project_name" : "Runner", "repo_handle" : { "host" : "bitbucket.org", "provider" : "bitbucket", , baseURL: https://appstoreconnect.apple.com/ci/api, response: , underlying error: The operation couldn’t be completed. (XcodeCloudCombineAPI.NetworkResponseError error 1.) Domain: OpenAPIRuntime.ClientError Code: 1 System Information: macOS Version 27.0 (Build 26A428)

Hello Apple Developer Community, I’m trying to connect a Bitbucket repository to Xcode Cloud through App Store Connect, but the connection consistently fails with an HTTP 403 response. Environment Product: Xcode Cloud / App Store Connect SCM: Bitbucket Cloud Integration: App Store Connect → Xcode Cloud → Bitbucket Date: September 15, 2026 Time: 3:51:44 PM IST / 10:21:44 UTC Apple Correlation ID: TIIRWMUD46W7OMZ7UDWXBRFI7E HTTP Status: 403 I have Administrator access in both App Store Connect/Apple Developer and the Bitbucket workspace/repository. What I have already checked I contacted Bitbucket Support and provided them with the browser network/HAR capture from the failed connection. Bitbucket confirmed that the App Store Connect Bitbucket callback returned HTTP 403. However, they explained that the browser capture cannot show the subsequent server-to-server communication between Apple/Xcode Cloud and Bitbucket. Bitbucket therefore asked Apple to investigate the server-side request using the Apple Correlation ID and timestamp. They indicated that the failure could potentially involve: Apple rejecting the Bitbucket OAuth callback. Apple receiving the callback but failing while processing it. A server-to-server request from Apple to Bitbucket returning an error. An OAuth authorization-code or access-token exchange failure. The 403 being generated by Apple's callback service. My question Has anyone experienced a similar HTTP 403 when connecting Bitbucket Cloud to Xcode Cloud through App Store Connect? Also, is there a known Xcode Cloud/App Store Connect requirement for Bitbucket OAuth or access tokens that could cause this type of 403 even when the user has administrator permissions? If an Apple engineer is able to review the server-side logs, could the following details help identify the failure? Apple Correlation ID: TIIRWMUD46W7OMZ7UDWXBRFI7E Timestamp: September 15, 2026, 10:21:44 UTC HTTP Status: 403 Bitbucket has already confirmed that the relevant server-to-server communication is not visible in the browser HAR, so I’m trying to determine which side is generating the 403 and at which stage of the OAuth flow it occurs. Any guidance from someone familiar with Xcode Cloud + Bitbucket integration would be greatly appreciated. Thank you.

Hello Apple Developer Community, I’m trying to connect a Bitbucket repository to Xcode Cloud through App Store Connect, but the connection consistently fails with an HTTP 403 response. Environment Product: Xcode Cloud / App Store Connect SCM: Bitbucket Cloud Integration: App Store Connect → Xcode Cloud → Bitbucket Date: September 15, 2026 Time: 3:51:44 PM IST / 10:21:44 UTC Apple Correlation ID: TIIRWMUD46W7OMZ7UDWXBRFI7E HTTP Status: 403 I have Administrator access in both App Store Connect/Apple Developer and the Bitbucket workspace/repository. What I have already checked I contacted Bitbucket Support and provided them with the browser network/HAR capture from the failed connection. Bitbucket confirmed that the App Store Connect Bitbucket callback returned HTTP 403. However, they explained that the browser capture cannot show the subsequent server-to-server communication between Apple/Xcode Cloud and Bitbucket. Bitbucket therefore asked Apple to investigate the server-side request using the Apple Correlation ID and timestamp. They indicated that the failure could potentially involve: Apple rejecting the Bitbucket OAuth callback. Apple receiving the callback but failing while processing it. A server-to-server request from Apple to Bitbucket returning an error. An OAuth authorization-code or access-token exchange failure. The 403 being generated by Apple's callback service. My question Has anyone experienced a similar HTTP 403 when connecting Bitbucket Cloud to Xcode Cloud through App Store Connect? Also, is there a known Xcode Cloud/App Store Connect requirement for Bitbucket OAuth or access tokens that could cause this type of 403 even when the user has administrator permissions? If an Apple engineer is able to review the server-side logs, could the following details help identify the failure? Apple Correlation ID: TIIRWMUD46W7OMZ7UDWXBRFI7E Timestamp: September 15, 2026, 10:21:44 UTC HTTP Status: 403 Bitbucket has already confirmed that the relevant server-to-server communication is not visible in the browser HAR, so I’m trying to determine which side is generating the 403 and at which stage of the OAuth flow it occurs. Any guidance from someone familiar with Xcode Cloud + Bitbucket integration would be greatly appreciated. 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:

While validating Xcode Cloud with a self-managed GitLab instance, I found what appears to be an OAuth scope issue affecting private repositories. Apple’s documentation says to configure the GitLab OAuth application with: api, read_repository, read_user However, the actual /oauth/authorize URL generated by Xcode Cloud requests only: scope=api+read_user With a private GitLab repository, OAuth completes successfully and Xcode Cloud can call: GET /api/v4/user → 200 GET /api/v4/projects/:project → 200 But repository setup fails with: Repository was not found. Either the repository does not exist or you do not have permission to access it. The GitLab user had Maintainer-or-higher access. I reproduced this from a clean Xcode Cloud setup. As a control test, I repeated the exact same flow but manually changed the OAuth authorization request to: scope=api+read_user+read_repository GitLab then explicitly requested read-only access to private repositories over Git HTTP. After authorization, the same private repository connected successfully to Xcode Cloud, and a build could be queued normally. A public repository works without read_repository, which can hide the issue. So the reproducible difference was: Private repo + Apple-generated api read_user → fails Private repo + api read_user read_repository → succeeds This also appears inconsistent with Apple’s own self-managed GitLab setup documentation, which instructs users to enable read_repository. I’m sharing this mainly for others who may run into the same issue with private repositories.