Hello, We are building a web extension that is running on all browsers. For Safari, i have used the "XCode Cloud Safari Extension Packager" tool. We have no Mac or anything to work with. For the first upload, there was no problem, and the app is currently published on Safari. Recently, we did on update on this web extension. So i thought i'd reuse the "XCode Cloud Safari Extension Packager" to upload my new version of the web extension. But there is always the following error for each build : Invalid Pre-Release Train. The train version '1.0' is closed for new build submissions This bundle is invalid. The value for key CFBundleShortVersionString [1.0] in the Info.plist file must contain a higher version than that of the previously approved version [1.0]. Please find more information about CFBundleShortVersionString at https://developer.apple.com/documentation/bundleresources/information_property_list/cfbundleshortversionstring Of course, the web extension manifest.json version is set to something else than "1.0". And i have created a new app version from the "Distrubution" pane in AppStoreConnect. But nothing helped. So my questions are the following : How do i set the version of the Safari Web Extension from AppStoreConnect when uploading a new ZIP ? How do Safari Extension Packager determine the version of the app if it is not from the manifest.json version ? Is it a bug from Safari Extension Packager or is there something i am missing ?

We started seeing an access issue today when attempting to go to the Xcode Cloud tab in App Store Connect. When you navigate to https://appstoreconnect.apple.com/teams/:teamId/apps/:appId/ci we're seeing the following message: The page you’re looking for can’t be found. The page you’re looking for does not exist, or you do not have permission to view it. I am the account holder so it shouldn't be a permissions issue. Is there an ongoing outage or problem in Xcode Cloud? And, if so, where can I monitor this accurately?

Hey, We're crunching to get our products ready for the announcements next week but are being slowed down by Xcode Cloud. Builds are failing and are extremely slow. We're using the latest Xcode beta and latest macOS release so we can upload our builds continuously to TestFlight. We're seeing builds taking up to almost an hour, even though takes around 10-15 minutes when it doesn't fail. The errors we're seeing seem to be timeout, for example: Showing All Errors Only The step invocation hit a user timeout. The xcodebuild build invocation timed out. No activity has been detected on stdout, stderr or the result bundle in 30 minutes. Here are links to some builds which have been restarted multiple times but keep failing for reasons out of our control. Please advice on how to get unblocked. https://appstoreconnect.apple.com/teams/69a6de80-3540-47e3-e053-5b8c7c11a4d1/apps/1102236212/ci/groups/8da12ae3-b454-4810-abe8-829f1af56a54 https://appstoreconnect.apple.com/teams/69a6de80-3540-47e3-e053-5b8c7c11a4d1/apps/1102236212/ci/groups/ee7b1fae-1363-4265-9d64-692434b7ebf2 https://appstoreconnect.apple.com/teams/69a6de80-3540-47e3-e053-5b8c7c11a4d1/apps/1102236212/ci/groups/fd915140-db2c-4b3b-bff4-16939c22665a

Any operation related to Xcode Cloud (e.g., viewing the dashboard, creating a workflow) fails immediately across all Xcode projects, including brand-new empty projects. The error is consistent and always appears as: API Invalid status code: 401. Domain: XcodeCloudCombineAPI.XCCResponseError Code: 1 System Information: macOS Version 15.6.1 (Build 24G90) "details" : "Error alert: API Invalid status code: 401.: XCCResponseError(responseErrorType: XcodeCloudCombineAPI.XCCResponseError.XCCResponseErrorType.invalidStatusCode(XcodeCloudCombineAPI.LegacyHttpStatus.unauthorized), requestUrl: Optional(https:\/\/appstoreconnect.apple.com\/ci\/api\/teams\/\/apps\/find?bundle_id=), traceId: Optional(\"2ab09bea8da9ef39\"), retryAfterSecsStr: nil, response: Optional(<NSHTTPURLResponse: 0x600000c6a800> { URL: https:\/\/appstoreconnect.apple.com\/ci\/api\/teams\/\/apps\/find?bundle_id=} { Status Code: 401, Headers {\n \"Content-Length\" = (\n 0\n );\n Date = (\n \"Fri, 05 Sep 2025 10:04:07 GMT\"\n );\n Server = (\n nginx\n );\n \"Set-Cookie\" = (\n \"dqsid=; Expires=Thu, 01 Jan 1970 00:00:00 GMT; Path=\/; Secure; HTTPOnly\",\n \"dqsid=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpYXQiOjE3NTcwNjY2NDQsImp0aSI6IlNQZ1FxVXd1UFF1UjI1X2wtZ2ZjN2cifQ.uoE9MRTx-TCY03Sw1qgMBcWrPVA8adtKd-nOZVwllS4; Max-Age=1800; Expires=Fri, 05 Sep 2025 10:34:04 GMT; Path=\/; Secure; HTTPOnly\"\n );\n \"Strict-Transport-Security\" = (\n \"max-age=31536000; includeSubDomains; preload\"\n );\n \"x-apple-jingle-correlation-key\" = (\n ZNGYRW2NJQJKAYDKU5FGCY6VVE\n );\n \"x-b3-traceid\" = (\n 2ab09bea8da9ef39\n );\n \"x-cache-status\" = (\n BYPASS\n );\n \"x-content-security-policy\" = (\n \"script-src 'self' *.apple.com\"\n );\n \"x-content-type-options\" = (\n nosniff\n );\n \"x-daiquiri-instance\" = (\n \"daiquiri:15751001:mr36p00it-hyhk07174801:7987:25RELEASE91:daiquiri-amp-dsce-asc-int-002-mr\",\n \"daiquiri:18493001:mr85p00it-hyhk03154801:7987:25RELEASE91:daiquiri-amp-all-shared-ext-001-mr\"\n );\n \"x-frame-options\" = (\n SAMEORIGIN\n );\n \"x-via\" = (\n \"2.0 PS-WUH-01zra68 [BYPASS]\"\n );\n \"x-ws-request-id\" = (\n \"68bab594_PS-WUH-01zra68_27159-54435\"\n );\n \"x-xss-protection\" = (\n \"1; mode=block\"\n );\n} }))\nError Description: Optional(\"API Invalid status code: 401.\")\nRecovery Suggestion: nil\nHelp Anchor: nil",

Hi everyone, Starting today, my Xcode Cloud CI workflow can no longer successfully build iOS/macOS/visionOS targets. The Archive step does not report any errors, but the xcodebuild command hangs indefinitely and eventually fails with the following message: The step invocation hit a user timeout. The xcodebuild archive invocation timed out. No activity has been detected on stdout, stderr or the result bundle in 30 minutes. My iOS and macOS targets can still be built, but the build time has increased by 2-3x compared to before. That's interesting. After I removed the visionOS target, the iOS target also failed to build. Additionally, since today, I’ve noticed a significant increase in network-related errors in Xcode Cloud. There have been multiple failures to download dependencies from Homebrew or GitHub. I have confirmed that CI versions which previously built successfully are now failing, while running the same build commands locally works fine. Based on these observations, I suspect there may be an issue with the Xcode Cloud environment itself. Has anyone else encountered similar problems? Any suggestions or updates would be appreciated! Thanks!

Hi everyone, After opting out of Xcode Cloud, I tried to set it up again for my product. However, I’m getting the following message when attempting to reconnect to my source control provider: "Connecting Xcode Cloud with your source control provider was incomplete. Products cannot be configured to use Xcode Cloud while your team’s opt-out request is being processed." It’s been 7 days since I opted out, and I still haven’t been able to re-enable Xcode Cloud. I’ve tried reconnecting both GitHub and Bitbucket, but the same message appears in both cases. I’d like to know: How long does the opt-out (deregistration) process usually take to complete? Is there any way to check the current status or expedite the reactivation process? Team Type: Organization Region: Japan Any insights or similar experiences would be greatly appreciated. Thank you in advance!

We want to replace our CI/CD pipelines in Azure DevOps with Xcode Cloud and are currently facing a critical hurdle. For some time now, we’ve observed that the PoC pipelines in Xcode Cloud are having major issues cloning our repositories stored on our Bitbucket Server. More and more pipeline runs are timing out because Xcode Cloud cannot receive the data. Today I spoke with our network team to check whether we might have an issue on our side affecting access to the repository, but we couldn’t find any problems. Cloning the repository to an external machine only takes 30 seconds, so the host’s bandwidth doesn’t seem to be the problem. However, our network specialists did discover one message: Significance: Request abnormal event: high total time Connection abnormal event: client has a slow receive rate If this is the bottleneck in the system, we may ultimately have to stay with Azure DevOps and Fastlane in order to continue providing our product teams with reliable builds. I look forward to your feedback and thank you in advance. Maik

Hey there. I'm experiencing a critical issue with Xcode Cloud builds for my macOS application (bundle ID: com.mymind.mymind-mac) where builds fail in Xcode Cloud with 7-8 errors, yet all logs indicate successful completion. Additionally, when manually uploading builds, they become stuck in "Processing" status indefinitely on App Store Connect. Issue Details: Problem: Xcode Cloud reports 7-8 build errors but logs show no fatal errors Secondary Issue: Builds uploaded to App Store Connect remain in "Processing" status indefinitely Platform: macOS application with Safari Web Extension Xcode Version: 26.1.1 (26B100) - Xcode 26.1 Build Environment: Xcode Cloud What Works: Package dependency resolution completes successfully Archive creation succeeds (** ARCHIVE SUCCEEDED **) Export succeeds (** EXPORT SUCCEEDED **) Provisioning profiles are created correctly Code signing completes without errors Manual upload to App Store Connect completes What Fails: Xcode Cloud: Build process fails with 7-8 errors, but no corresponding errors in logs App Store Connect: Builds remain stuck in "Processing" status and never become available for TestFlight or submission Logs Examined: All logs indicate successful completion with no fatal errors: xcodebuild-archive.log - Shows ** ARCHIVE SUCCEEDED ** xcodebuild-export-archive.log - Shows ** EXPORT SUCCEEDED ** resolve_package_dependencies.log - All packages resolved successfully IDEDistribution_standard.log - All distribution steps complete IDEDistributionPipeline.log - Packaging succeeds, code signing succeeds IDEDistributionProvisioning.log - Provisioning profiles created successfully IDEDistribution_critical.log - Only shows deprecated command warning Only Warning Found: App Store Connect request for store configuration failed for account Session Proxy Provider Unable to authenticate with App Store Connect (Error Domain=DVTITunesSoftwareServiceFoundation.DVTServicesSessionProviderCredentialITunesAuthenticationContextError Code=1) Failed to find an account with App Store Connect access for team XXXXXXX This warning appears non-fatal as the export completes successfully afterward. Xcode Cloud Behavior: Xcode Cloud dashboard shows 7-8 errors No error details are visible in the Xcode Cloud UI All log files downloaded from Xcode Cloud show successful completion Build artifacts are created successfully App Store Connect Behavior: Builds upload successfully (confirmed via Xcode) Build appears in App Store Connect with correct version/build number Status shows "Processing" with spinning indicator Build never completes processing (tested for 24+ hours) No email notifications about processing failures App Configuration: macOS application (minimum version: macOS 12.0) Includes Safari Web Extension (SafariWebExtension.appex) Includes Lottie framework Uses automatic signing with managed provisioning profiles Also tried with manual signing Both Development and Distribution certificates valid until November 2026 Questions: Why does Xcode Cloud report 7-8 errors when all logs show successful completion? Where can I find the actual error details? Why do builds remain stuck in "Processing" on App Store Connect? Is there a backend validation failing that isn't being reported? Are there additional diagnostic logs that would show the actual errors Xcode Cloud is detecting? Is this related to the App Store Connect authentication warning? The logs suggest Xcode Cloud can't authenticate with App Store Connect properly, despite having valid credentials. Could this be related to Xcode 26.1.1 (26.1) compatibility with Xcode Cloud or App Store Connect processing? Steps Taken: Verified all certificates and provisioning profiles are valid Tested local builds and manual uploads (upload succeeds) Reviewed all available log files Waited 24+ hours for App Store Connect processing Tested both development and distribution exports (both succeed) This issue is completely blocking our automated CI/CD pipeline and preventing us from releasing updates to the App Store. We cannot use Xcode Cloud for its intended purpose, and even manual workarounds fail at the App Store Connect processing stage. Any hints or ideas would be welcome.

This happens way too often (see the image below). Especially today. I used this snippet from the offical Rust website to install rustup: curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh -s -- -y Run ci_post_clone.sh script Run command: 'cd /Volumes/workspace/repository/apps/app/ios/ci_scripts && /Volumes/workspace/repository/apps/app/ios/ci_scripts/ci_post_clone.sh' info: downloading installer warn: curl: (6) Could not resolve host: static.rust-lang.org curl: (6) Could not resolve host: static.rust-lang.org curl: (6) Could not resolve host: static.rust-lang.org curl: (6) Could not resolve host: static.rust-lang.org error: command failed: downloader https://static.rust-lang.org/rustup/dist/x86_64-apple-darwin/rustup-init /var/folders/6h/_32gb9js77g6c54h3q7g6q1h0000gn/T/tmp.yave38jqWa/rustup-init x86_64-apple-darwin Error: Command exited with non-zero exit-code: 1 Warning: Running ci_post_clone.sh script failed (exited with code 1). Executable scripts are run using the interpreter specified in the shebang line.

Dear Xcode cloud support. on 30.1.2026 Xcode cloud was not able to connect to our git server. so I deleted the repository from app store connect Xcode cloud settings and deleted the Xcode cloud in app store connect for all our apps. I started to create Xcode cloud workflow from Xcode and when I want to Grant Access - Register GitLab Application - to our git repository I get and error : "504 Client Timeout. If you are using a firewall, it must be configured to accept incoming connections." git is behind VPN but the IP address ranges 17.58.0.0/18, 17.58.192.0/18, and 57.103.0.0/22 are white labeled and before 30.1.2026 it was working. I contacted the gitlab administrators and they acknowledged that during "Register GitLab Application" they see no traffic (in gltlab and proxy server) from xcode cloud. I tried "Register GitLab Application" multiple times until now with same error. It is not app specific because this error happens for all our apps. Thanks a lot yours sincerely, Zoltan Bognar More Info: Source Control Provider: git-lab self-managed, tested with web browser: safari, chrome I can provide additional info like Primary repository, App store team ID, Entity Name, Link to repository, Application ID to grant access, and bundle id. if needed.

Log shows: Run command: 'xcodebuild -exportArchive -archivePath /Volumes/workspace/tmp/d3c9c43f-e24e-4ad9-882d-d0179ab3149b.xcarchive -exportPath /Volumes/workspace/developmentexport -exportOptionsPlist /Volumes/workspace/ci/development-exportoptions.plist '-DVTPortalRequest.Endpoint=http://172.16.182.66:8089' -DVTProvisioningIsManaged=YES -IDEDistributionLogDirectory=/Volumes/workspace/tmp/development-export-archive-logs -DVTSkipCertificateValidityCheck=YES -DVTServicesLogLevel=3' Command exited with non-zero exit-code: 70

I'm using Xcode Cloud for release builds and unit tests, and it works fine. Recently, I added some XCUITests, but to run it the way I need I started to use this mock server. Basically, the idea is you define before each test what responses you want to get for specific requests. It works like a charm locally. But if I want to run it in Xcode Cloud, it looks like the server has failed to launch. The mock server is a separately launched binary file. I think this is because this permission I get when launch it locally. So, my question is how to allow this kind of permission in Xcode Cloud to make my UITests works correctly? You can find a detailed instruction how server is launched on a github page I provided.

Possible a duplicate of this resolved post from November, but I can't access any Xcode Cloud artefacts with the message "You are not authorized to access this team’s resources." Trying to access from within Xcode itself crashes Xcode 🙃

Since today, all our team members cannot download artifacts from Xcode Cloud builds. We get a JSON response that contains: {"message":"You are not authorized to access this team’s resources."} System Status doesn't show any issues at the time. Is there an action we can follow to restore proper access? Thank you in advance.

My Xcode Cloud workflows tell me the 'Latest Release' Xcode that it's using is Xcode 16.1 Release Candidate (16B40) Obviously that is well out of date at this point, plus, an RC is not a release version. How can I tell Xcode Cloud to always use the latest (non-RC) release version?

Xcode Cloud is unable to run unit tests for a MacOS target after adding a restricted capability (keychain-access-groups). Have tried setting both manual and automatic signing (with a Mac OS development profile). The tests run on my locally fine, but when pushed to Xcode Cloud the crash report indicates a Code Signing Issue, downloading the Artifact for Test Products for AppTests and viewing the app contents I noted that when built locally embedded.provisionprofile appears within the App/Contents that doesn't appear in Xcode Cloud. To reproduce, create a new MacOS app with a test plan, run a Test job (successfully runs) then add the capability for Keychain Sharing: <array> <string>$(AppIdentifierPrefix)com.transmedics.RemoteView.group</string> </array> to the entitlements. Run the job again and tests with the project fails in Xcode Cloud, with code signing issues in the crash report.

My app is approved for the Web Browser Public Key Credential Request managed capability and has it added to its App ID Configuration: It has been added to my entitlements file: I am able to build and run unit tests in Xcode locally using my managed profile. When I push changes and Xcode Cloud tries to build and run the app, I get the following error: Mirrai encountered an error (Failed to install or launch the test runner. (Underlying Error: Could not launch “MirraiTests”. Runningboard has returned error 5. Please check the system logs for the underlying cause of the error. (Underlying Error: The operation couldn’t be completed. Launch failed. (Underlying Error: Launchd job spawn failed)))) Removing just the com.apple.developer.web-browser.public-key-credential entitlement, with no other changes, results in all tests passing on Xcode Cloud. Some thoughts: In project settings, the test target has a different bundle id (appending Tests to the app bundle id). Under "Certificates, Identifiers & Profiles," the managed capability is added to the bundle id but it is an explicit bundle id and not a wildcard. Do I need to apply for the managed capability for the test bundle id as well? Or for a wildcard bundle id? xcodebuild-test-without-building.log

When building xcode project of an application with login item included/embedded (another target), locally it works without problems. But when building on xcode cloud, we are getting the error: ITMS-90286: Invalid code signing entitlements - Your application bundle’s signature contains code signing entitlements that aren’t supported on macOS. Specifically, the “XXX.***.***” value for the com.apple.application-identifier key in “Path_to_login_Item” isn’t supported. This value should be a string that starts with your Team ID, followed by a dot (“.”), followed by the bundle ID. If there are no capabilities added to the login item's target (only com.apple.security.inherit and App Sandbox), the project builds without errors. But our login item needs to access a database in app group container and sync its data with iCloud, so after adding iCloud and App Group entitlements, building on xcode cloud fails with the error written above. Locally it builds and runs without problems. So, what should be done to fix this issue when building on xcode cloud?

I'm setting up a first workflow in Xcode Cloud and when I go through the flow and reach the 'Grant Access to your source code' pane, my projects repo is listed as primary and has a green checkmark next to it, but one of my SPM dependencies does not. When I press the 'Grant Access' it launches AppStoreConnect which complains the repo can't be found or I don't have the correct admin permissions. I'm using BitBucket Cloud and both repos are mine and I am the admin for both. Xcode itself will build the dependency locally correctly. I did see that the dependent SPM package needs a Package.resolved checked in, which I've now done, but I can still no longer get past the Grant Access step. When I try to add myself as admin to the dependent repo, BitBucket says I can't be added because I'm already an admin. This is the same for the projects primary repo as well. But Xcode still thinks I only have read access. How do I get passed this? Xcode isn't even telling me what repo is troublesome: { "category" : "xcode-cloud-data", "column" : "23", "subsystem" : "com.apple.dt.XcodeCloudKit", "details" : "Error alert: You must have Admin or Write access to your repository. Your current permission level is read.: ModelErrorResponseError(error: XcodeCloudAPI.Components.Schemas.ErrorResponse(message: \"You must have Admin or Write access to your repository. Your current permission level is read.\", errorKey: nil, helpUrl: nil, details: [], body: nil, actions: []), httpStatus: XcodeCloudCombineAPI.LegacyHttpStatus.badRequest, traceId: Optional(\"ee71bf64b8cf2c27\"), requestUrl: Optional(https:\/\/appstoreconnect.apple.com\/ci\/api\/teams\/69a6de89-4b61-47e3-e053-5b8c7c11a4d1\/products-v2\/A80C7CA9-25F0-4DCA-B7CC-D789A5022B88))\nError Description: Optional(\"You must have Admin or Write access to your repository. Your current permission level is read.\")\nRecovery Suggestion: nil\nHelp Anchor: nil", "createdAt" : "2025-06-28T18:49:15Z", "level" : "info", "filename" : "Logger+Additions.swift", "funcName" : "logError(_:)", "line" : "36" },

Dear all, For an important client, we are currently experiencing issues related to performance IOS build using Xcode Cloud. More in detail, their build process is taking approximately 30 minutes to complete at the moment, whereas the same build executed locally on a Mac machine takes around 7 minutes. This significant difference in build times is causing concerns and slowing down the development work. We would appreciate your support in identifying possible causes and exploring different ways to improve the actual situation (ex if it is possible to increase the Cloud machine calculation power). Could you please advise us on how we might proceed to analyze and potentially optimize the build times on Xcode Cloud? What kind of processors are used? Any guidance, best practices, or diagnostic steps you can suggest would be greatly appreciated. Looking forward to your support.