After a break using AWS Macs for CI we are willing to give Xcode cloud another go. Unfortunately we are unable to complete the "Grant Access to your Source Code" step. We tried multiple accounts including maintainer, owner and admin. We tried from multiple Macs and versions of macOS. "Connecting Xcode Cloud with your source control provider was incomplete. 503 Service Unavailable. Please ensure that your repository is available and accepting connections."

Recently, I have trouble with my Xcode Cloud builds, where they seemingly complete, but the very final step does not happen. I am building from the same codebase for both macOS and iOS (I have two “Archive” steps in my workflow, one for iOS and one for macOS). The iOS one usually completes fast without problems. The macOS log ending looks like this, and remains stuck forever, with the macOS build in the “spinning progress” state and never completing. Is there something I can do on my end to make this work better? I would not want to go back to manual builds, Xcode Cloud is convenient and was working well for a while, but this is really annoying lately.

I have an app I am toying with and I am seeing the following error in github's Xcode automation from Apple. My other apps work fine fine in xcode cloud with the same project setup. Run scheme_list=$(xcodebuild -list -json | tr -d "\n") 2025-02-05 03:15:56.669 xcodebuild[2841:17672] Writing error result bundle to /var/folders/2s/h6hvv9ps03xgz_krkkstvq_r0000gn/T/ResultBundle_2025-05-02_03-15-0056.xcresult xcodebuild: error: Unable to read project 'Legacy Letters.xcodeproj'. Reason: The project ‘Legacy Letters’ cannot be opened because it is in a future Xcode project file format (70). Adjust the project format using a compatible version of Xcode to allow it to be opened by this version of Xcode. /opt/homebrew/Cellar/ruby@3.0/3.0.7/lib/ruby/3.0.0/json/common.rb:216:in `parse': 809: unexpected token at '' (JSON::ParserError) from /opt/homebrew/Cellar/ruby@3.0/3.0.7/lib/ruby/3.0.0/json/common.rb:216:in `parse' from -e:1:in `<main>'

Xcode 16.2 Framework Signing Issues with Cloud Managed Developer ID in Automated Builds Issue Description After upgrading from Xcode 15.4 to 16.2, our macOS app's frameworks are failing notarization with the error "The binary is not signed with a valid Developer ID certificate" for embedded frameworks when building through fastlane. This worked correctly in Xcode 15.4. Importantly, manually archiving and notarizing through the Xcode GUI still works correctly - the issue only occurs during automated builds. Build Configuration We use fastlane to build and notarize our macOS app: build_mac_app( scheme: 'Runner', export_method: "developer-id", xcargs: '-allowProvisioningUpdates' ) This generates the following xcodebuild commands: Archive: xcodebuild -workspace ./Runner.xcworkspace -scheme Runner -destination 'generic/platform=macOS' -archivePath /path/to/archive -allowProvisioningUpdates archive Export with plist: xcrun -exportArchive -exportOptionsPlist '/path/to/plist' -archivePath /path/to/archive -exportPath '/output/path' -allowProvisioningUpdates Export options plist contents: &amp;lt;?xml version="1.0" encoding="UTF-8"?&amp;gt; &amp;lt;!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"&amp;gt; &amp;lt;plist version="1.0"&amp;gt; &amp;lt;dict&amp;gt; &amp;lt;key&amp;gt;installerSigningCertificate&amp;lt;/key&amp;gt; &amp;lt;string&amp;gt;Developer ID Installer: Company Inc (1234567891)&amp;lt;/string&amp;gt; &amp;lt;key&amp;gt;method&amp;lt;/key&amp;gt; &amp;lt;string&amp;gt;developer-id&amp;lt;/string&amp;gt; &amp;lt;key&amp;gt;signingStyle&amp;lt;/key&amp;gt; &amp;lt;string&amp;gt;automatic&amp;lt;/string&amp;gt; &amp;lt;/dict&amp;gt; &amp;lt;/plist&amp;gt; Notarization: ditto -c -k --rsrc --keepParent "My App.app" "My App.app.zip" xcrun notarytool submit "My App.app.zip" --output-format json --wait --key /path/to/key --key-id ABCDEFGHIJ --issuer 12345678-abcd-1234-5678-fc2d96b1735a Error Output Notarization fails with the following errors: { "severity": "error", "code": null, "path": "My App.app.zip/My App.app/Contents/Frameworks/some_package.framework/Versions/A/some_package", "message": "The binary is not signed with a valid Developer ID certificate.", "docUrl": "https://developer.apple.com/documentation/security/notarizing_macos_software_before_distribution/resolving_common_notarization_issues#3087721", "architecture": "arm64" } Key Details Using Xcode Cloud managed Developer ID certificates (not local certificates) ✅ Building, archiving, and notarizing through Xcode GUI works correctly Automatic signing is enabled Expected Behavior Frameworks should be automatically signed with the cloud managed Developer ID certificate during the export process, as they were in Xcode 15.4. Has there been a change in how framework signing is handled with cloud managed certificates in Xcode 16.2's command line tools? Any guidance on how to ensure frameworks are properly signed during automated builds when using automatic signing with cloud managed Developer ID certificates would be appreciated.

I've recently added iCloud backup on my chat app. Conversations are backing up fine but some users are losing their chats and when I see the telemetry it show "BAD_REQUEST" error. I couldn't find any details or solution for it. Does anyone has any idea what it could be? My development scheme is already fully deployed to production.

Recently, I’ve noticed that the Archive workflow on Xcode Cloud frequently fails randomly with the following error: ❌ Exporting for App Store Distribution failed. Please download the logs artifact for more information I’m not sure if this issue is on my side or if it’s related to Xcode Cloud itself. Has anyone encountered a similar problem?

Hello guys, I currently have a problem with Xcode cloud. When I setup a simple workflow in my Xcode project that just archives it and builds the project for TestFlight Internal testing, it will fail and give the following error: Invalid Signature. Code failed to satisfy specified code requirement(s). The file at path “DropIn.app/DropIn” is not properly signed. Make sure you have signed your application with a distribution certificate, not an ad hoc certificate or a development certificate. Verify that the code signing settings in Xcode are correct at the target level (which override any values at the project level). Additionally, make sure the bundle you are uploading was built using a Release target in Xcode, not a Simulator target. If you are certain your code signing settings are correct, choose “Clean All” in Xcode, delete the “build” directory in the Finder, and rebuild your release target. For more information, please consult https://developer.apple.com/support/code-signing. I've already been searching for solutions and double checked the documentation. My Xcode project is a simple iOS app with the app target and two other targets for tests and UI tests. I made sure the checkbox "Automatically manage signing" is ticked in all targets. The workflow has only one action "Archive - iOS" with TestFlight (Internal Testing Only) and a post-action "TestFlight Internal Testing - iOS" with an internal testing group assigned. I've seen people having similar problems where it turned out they had a non roman character in their name? This would also affect me if that's the case, since my name includes "ö". I also checked on app store connect and already deleted xcode cloud data, removed all certificates recreated the workflow, but it still gives this error. Any ideas on how to fix this?

Hi everyone, we're experiencing problems with our unit test builds on Xcode cloud. Without having changed anything in our build configuration, we're getting failed builds (that also take a loooong time) withour any of the build / test steps showing any sign of failures. Maybe related: the "Save artifacts" step of the build appears to have taken almost an hour, but its individual sub-steps only took seconds. Is anyone else having those problems as well? -Gereon

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",

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.

Dear We try to generate IPA with Xcode Cloud but this task fail in Export archive phase (Export archive for app-store distribution). The error that appear in the archive logs is: error: exportArchive Provisioning profile "iOS Team Store Provisioning Profile: cl.app.myapp" doesn't include the com.apple.CommCenter.fine-grained entitlement. Any idea about to resolve this problem ? king regards

We are encountering build failures during the following stages on Xcode Cloud: • Export archive for ad-hoc distribution -> fail • Export archive for development distribution -> fail • Export archive for app-store distribution -> fail Run command: 'xcodebuild -exportArchive -archivePath /Volumes/workspace/tmp/a603f613-f0a2-4053-9316-2f25ca93250d.xcarchive -exportPath /Volumes/workspace/adhocexport -exportOptionsPlist /Volumes/workspace/ci/ad-hoc-exportoptions.plist '-DVTPortalRequest.Endpoint=http://172.16.56.69:8089' -DVTProvisioningIsManaged=YES -IDEDistributionLogDirectory=/Volumes/workspace/tmp/ad-hoc-export-archive-logs -DVTSkipCertificateValidityCheck=YES -DVTServicesLogLevel=3' Error Command exited with non-zero exit-code: 70 2025-01-21T05:11:20.962717086Z error: exportArchive There is a problem with the request entity 2025-01-21T05:11:20.962756880Z 2025-01-21T05:11:20.962760011Z error: exportArchive No signing certificate "iOS Distribution" found 2025-01-21T05:11:20.962764378Z 2025-01-21T05:11:20.962767137Z error: exportArchive There is a problem with the request entity 2025-01-21T05:11:20.962771440Z 2025-01-21T05:11:20.962774232Z error: exportArchive No signing certificate "iOS Distribution" found The build process was functioning correctly until this morning with same branch. We also have verified that our certificates are valid and successfully uploaded to TestFlight using these certificates on the local Xcode environment. This appears to be an issue on the Xcode Cloud side as no significant configuration changes were made on our end.

I'm trying to set up Xcode Cloud for the first time. When I go through the "Get Started" flow and get to "Grant Access to Your Source Code" step, when I click the "Grant Access" button, I get "This Operation Could Not Be Completed." It has the correct URL to my Github repo. Github is working fine in Xcode itself: I can push and pull changes and view repo history. I've tried: restarting Xcode rebooting the Mac Removing the Github account from Xcode and adding it back Creating a new Github personal token and removing the Github account from Xcode and using the new token to add it back I've looked through my Github settings and don't see anything that might cause an issue. I filed FB16511549 to report this. The error dialog in Xcode automatically filled the feedback fields, and says: "API Invalid status code: 500. XcodeCloudCombineAPI.XCCResponseError:1" I'm running Xcode 16.2 (16C5032a) on an M4 MacBook Pro running Sequoia 15.3.1 (24D70). Does anyone have any insights or ideas of other things to try? Thanks.

We are getting unreliable results on XCode Cloud tests. I'm not sure if it's related to the current service outage. I'm running a very simple XCTest UI suite, on some devices it succeds and it others it fails to start. I'm not getting a userful error message. MyApp-Runner encountered an error (Failed to prepare device 'iPhone 16 Pro Max' for impending launch. (Underlying Error: Unable to boot the Simulator. launchd failed to respond. (Underlying Error: Failed to start launchd_sim: could not bind to session, launchd_sim may have crashed or quit responding)))

Am I doing something wrong? FB18269317

Hello, When archiving a binary with Xcode, I've always kept my archives in the Organizer so I can symbolicate crash logs using the dSYM files. I've been thinking about moving to Xcode Cloud for archiving. Will crash logs still be symbolicated and readable in the Xcode Organizer? Thank you, Axel