Hello, my builds keep failing in Xcode Cloud at the creation of the archive for tesflight. I am receiving an email mentioning "ITMS-90035: Invalid Signature" TMS-90035: Invalid Signature - Code failed to satisfy specified code requirement(s). The file at path “BASELog.app/BASELog” 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. The thing is the archives which are not intended for testflight not App Store connect are not failing. I think I have the required distribution certificates (initially they were created by API for Xcode Icloud, I add 3, revoked them and recreated one manually and the other from Xcode directly) : even though certificats seems ok, in Xcode I see a dev certificate in the managed release and if I try to force a distribution certificate in the build I then get the following warning It looks like my managed profile is not behaving properly, like not embedding a distribution certificate. I looked on the web for the signing issues, and I have found in other threads an issue with assets having special charsets. I checked on my side, the only thing I see is my app icon is named "icon_v1.png" I assume it shouldn't be an issue. I dont see any special char anywhere else in the sources name. Anyone has any idea on what is causing those build fails on the archive?

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.

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: <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>installerSigningCertificate</key> <string>Developer ID Installer: Company Inc (1234567891)</string> <key>method</key> <string>developer-id</string> <key>signingStyle</key> <string>automatic</string> </dict> </plist> 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'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.

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?

Since first beta of iOS 26 I've created a workflow where I can deploy to TestFlight the builds compiled using the iOS 26 SDK, and it has worked fine until yesterday when I started receiving this error: Unsupported SDK or Xcode version. Your app was built with an SDK or version of Xcode that isn’t supported. Although you can use beta versions of SDKs and Xcode to build and upload apps to App Store Connect, you need to use the latest Release Candidates (RC) for SDKs and Xcode to submit the app. For details on currently supported SDKs and versions of Xcode, visit: https://developer.apple.com/news/releases. I haven't changed anything in the workflow so I suspect it's a bug on Apple side? Or am I missing something? It is set to use "Latest Beta or Release" for both Xcode and macOS, archive and deploy to TestFlight Internal Testing. Thank you!

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!

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

Trying to submit a build to TF from Xcode 26 via Xcode Cloud (both for iOS and macOS). The operation fails with this message: Missing app icon. Include a large app icon as a 1024 by 1024 pixel PNG for the 'Any Appearance' image well in the asset catalog of apps built for iOS or iPadOS. Without this icon, apps can't be submitted for review. For details, visit: https://developer.apple.com/documentation/xcode/configuring-your-app-icon. If you’ve added an icon made with Icon Composer, visit https://developer.apple.com/app-store-connect/release-notes/ for details about known issues. I thought it's because Icon Composer icons may not be supported yet, but then that last sentence is confusing me. Does this mean that TF just won't support Xcode 26 uploads yet, or does it accept them and I need to provide legacy icons for my build?

I'm currently using another provider for CI/CD. They've been offering Apple Silicon builds for over a year now. When we switched over, we saw our build times cut in half. I've seen similar results locally, back when I bought an M1 Mac. So, recently, I tried to use Xcode Cloud on my project. My build time is nearly 45 minutes, where my build time on my current system is about 15 minutes, max. Since I work on a team, and we make regular commits, having a 45 minute turnaround is not ideal. When I looked at the logs of my Xcode Cloud project, I saw a lot "x86_64" stuff in there, which led me to believe that Xcode Cloud is still building on Intel machines. Additionally, I run tests on my builds. The build time alone (before running tests) was almost 20 minutes. The 15-minute time I cited with my current CI/CD included build time & tests running. So, a whole cycle finishes on my current setup before tests are even run. I noticed that there was a bunch of x86_64 in the logs, which made me think that Xcode Cloud is still using Intel. Is this true? I've just gotten really used to faster build times, and I can't move onto a system like this, where the times are so drastically different. Like, I wouldn't mind build time that would add only a few more minutes to what I have now. But going from 15 -> 45 minutes is a real problem.

Hello, I'm getting started for my project with Xcode Cloud since I upgraded to the macOS Sequioa Beta and Xcode 16 now refuses to archive builds for TestFlight. Somewhere very late in the build process I get the following error: realitytool requires Metal for this operation and it is not available in this build environment The log says this happens at: Compile Skybox urban.skybox My project uses RealityKit. How can I fix this issue? Thanks!

Our UITests are failing because Simulator won't start up. What can I do here? Workflow Settings: Sequoia 15.1 Xcode 16.1 Testing on iPad and iPhone 17.5 simulators Thank you in advance

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)))

Hi everyone, I’m unable to enable Xcode Cloud for any app on my account. At the final step of the Xcode workflow setup (“Confirm App on App Store Connect”), pressing Complete always returns: “ could not be added to Xcode Cloud. Authentication credentials are invalid.” This affects both existing apps and completely new test apps with fresh bundle IDs. What I’ve verified • I am Account Holder and Admin. • All agreements are accepted. • App creation, bundle ID registration, and certificate management work normally. • I’ve removed/re-added my Apple ID in Xcode and cleared all Xcode-* tokens from Keychain. • Test apps in clean Git repos reproduce the same error. Support I have already opened Case ID 102769512657 with Apple Developer Support, but I’m posting here in case others have seen this issue or know of additional steps to confirm the provisioning state.

Hello, Has anyone used Sentry with Xcode Cloud? How are you uploading dSYM files? One way is fastlane but Xcode Cloud doesn't come with Fastlane preinstalled, the other is sentry-cli but the same issue, it's not preinstalled.

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.

Hello, I uploaded a new build to TestFlight, and it has been about an hour since the processing was completed. However, the update is still not showing up in the TestFlight app. From my experience, the update usually appears within 10 to 30 minutes, but this time it is taking unusually long. I’m wondering if anyone else has experienced a similar issue and found a solution. Any advice or guidance would be greatly appreciated. Thank you!

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?

We have a simple workflow that just runs the Test action on my unit_tests scheme (see Xcode Cloud workflow configuration screenshot). The workflow is configured to use Xcode 16.4 (Latest Release), macOS Sequoia 15.6 (Latest Release), and iOS 18.0 simulators. Today, this workflow has been consistently running indefinitely. The Xcode cloud runner tries to launch the simulator to execute the tests, but it fails. See the error message in the screenshot from Xcode Cloud logs. Link to corresponding build is in my Feedback Assistant ticket. It continues to retry this operation for a very long time — I had one job that ran for over 90 minutes. Link to corresponding build also in that same Feedback Assistant ticket. Are Xcode Cloud runners perhaps currently undergoing maintenance? Or is something else going on. I would appreciate if Xcode Cloud usage from today could be refunded to my team’s account. Feedback Assistant ticket #FB20195292. Error message: MyApp encountered an error (Failed to prepare device 'iPhone 16' 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)))

Hi there, We’re encountering this error in all of our builds when using the latest Xcode and macOS: The Metal Toolchain was not installed and could not compile the Metal source files. Download the Metal Toolchain from Xcode > Settings > Components and try again. In short, all builds are failing. I’ve tried fixing this by installing Metal and applying other solutions, but none of them worked reliably. Is there a way to ensure that the Metal Toolchain is installed on the CI machine?