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?
Xcode Cloud
RSS for tagAutomate workflows to test, analyze, build, and distribute your app, and integrate them with other developer tools, such as TestFlight and App Store Connect.
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
I am experiencing an issue where Xcode Cloud is not available in my Apple Developer Program account on App Store Connect. Despite having an active developer membership, I cannot access or enable Xcode Cloud for my apps.
Could you please assist me in understanding why this feature is not available for my account and what steps I need to take to enable it?
We just changed the repository from Bitbucket > Github. While all connected successfully, none of the branches are appearing.
I understand usually it takes time (cache etc) but its been a good few hours.
Also tried to remove the integration and re-setup but to no avail.
I'm getting this error, don't really understand why...
Showing All Errors Only
Build Archive
Export archive for ad-hoc distribution
Command exited with non-zero exit-code: 70
Command exited with non-zero exit-code: 70
Export archive for development distribution
Command exited with non-zero exit-code: 70
Command exited with non-zero exit-code: 70
Export archive for app-store distribution
Command exited with non-zero exit-code: 70
Command exited with non-zero exit-code: 70
Activity Log Complete 6/26/25, 10:06 PM 0.4 seconds
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?
Topic:
Developer Tools & Services
SubTopic:
Xcode Cloud
Can anyone help me resolve this lookup issue? This has been breaking builds for months. We make no changes and after a couple hours it works.
It seems like Apple resolvers are getting a failure and then negatively caching the failure. Immediate subsequent runs extend the failure duration
this is one of our installs from a pod install
installing onnxruntime-c (1.21.0)
[!] Error installing onnxruntime-c
[!] /usr/bin/curl -f -L -o /Volumes/workspace/tmp/d20250730-29606-1v7ovh/file.zip https://download.onnxruntime.ai/pod-archive-onnxruntime-c-1.21.0.zip --create-dirs --netrc-optional --retry 2 -A 'CocoaPods/1.16.2 cocoapods-downloader/2.1'
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0curl: (6) Could not resolve host: download.onnxruntime.ai
Topic:
Developer Tools & Services
SubTopic:
Xcode Cloud
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 have Admin role but whenever I select the tab "Xcode Cloud" on any app, the page is not loaded.
I am developer from Russia, its banned for russian users???
Please help, i cant update app
Topic:
Developer Tools & Services
SubTopic:
Xcode Cloud
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?
I struggling in getting Xcode Cloud to work with a stand alone watch app. This app has the following three targets and each bundle identifier is set up in the Identifiers section of the developer portal.
iphone container target called Unleashed abc.xyz.Unleashed
watch target called Unleashed Watch App abc.xyz.Unleashed.watchkitapp
watch target called Unleashed WidgetExtension abc.xyz.Unleashed.watchkitapp.Unleashed-Widget
I have a App Store provisioning set up for abc.xyz.Unleashed.watchkitapp
The app runs fine in the watch simulator, but fails with the following when I do an Xcode Cloud build
Export archive for ad-hoc distribution
Export archive for development distribution
Export archive for app-store distribution
When I expand each one of these errors it reports:
Command exited with non-zero exit-code: 70
I also tried archiving the project in Xcode then selected the Archive but it won't let me validate because that button is disabled.
Very confused I have successfully used Xcode Cloud for a phone app but am having a problem with this watch app that has a widget
I have two apps in App Store Connect (same app but different bundle IDs), and I would like to manage workflows for both. However, when configuring workflows, although both apps appear on the list for configuration at first, selecting and configuring the first will be the only app available, since after that, there's no way to add the other app. It looks like a bug, but I couldn't find any additional reports of this case while browsing the web.
I've been running into issues with Xcode Cloud/my workflow when it's trying to archive the app. I've tested locally and both archiving and building the app for release works.
I've tried a few things to clear it.
pod deintegrate and pod install
Checking off "archive" for the build scheme
Creating a certificate for both development and distribution. I made sure automatic signing was enabled as well.
I have a ci_scripts/ci_post_clone.sh script that successfully completes.
Have tried setting the xcode version of the workflow to 16.2 which is what my local xcode version is. I've switched it back to the latest, 16.4.
running pod update
Updating flutter
However, I consistently get the following 2 errors :
`Showing All Messages
Run command: 'xcodebuild archive -workspace /Volumes/workspace/repository/ios/Runner.xcworkspace -scheme Runner -destination generic/platform=iOS -archivePath /Volumes/workspace/build.xcarchive -derivedDataPath /Volumes/workspace/DerivedData -resultBundleVersion 3 -resultBundlePath /Volumes/workspace/resultbundle.xcresult -resultStreamPath /Volumes/workspace/tmp/resultBundleStreame3592434-5b88-48da-a3c4-f750abee4d08.json -IDEPostProgressNotifications=YES CODE_SIGN_IDENTITY=- AD_HOC_CODE_SIGNING_ALLOWED=YES CODE_SIGN_STYLE=Automatic DEVELOPMENT_TEAM=JG794CQD68 COMPILER_INDEX_STORE_ENABLE=NO -hideShellScriptEnvironment'
`
and
Showing All Messages
Unhandled exception:
ProcessException: No such file or directory
Command: /Users/local/flutter/bin/flutter assemble --no-version-check --output=/Volumes/workspace/DerivedData/Build/Intermediates.noindex/ArchiveIntermediates/Runner/BuildProductsPath/Release-iphoneos/ -dTargetPlatform=ios -dTargetFile=lib/main.dart -dBuildMode=release -dConfiguration=Release -dIosArchs=arm64 -dSdkRoot=/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS18.5.sdk -dSplitDebugInfo= -dTreeShakeIcons=true -dTrackWidgetCreation=false -dDartObfuscation=false -dAction=install -dFrontendServerStarterPath= --ExtraGenSnapshotOptions= --DartDefines=RkxVVFRFUl9WRVJTSU9OPTMuMzUuMQ==,RkxVVFRFUl9DSEFOTkVMPXN0YWJsZQ==,RkxVVFRFUl9HSVRfVVJMPWh0dHA6Ly9naXRodWIuY29tL2ZsdXR0ZXIvZmx1dHRlci5naXQ=,RkxVVFRFUl9GUkFNRVdPUktfUkVWSVNJT049MjBmODI3NDkzOQ==,RkxVVFRFUl9FTkdJTkVfUkVWSVNJT049MWU5YTgxMWJmOA==,RkxVVFRFUl9EQVJUX1ZFUlNJT049My45LjA= --ExtraFrontEndOptions= -dSrcRoot=/Volumes/workspace/repository/ios -dTargetDeviceOSVersion= -dCodesignIdentity=- release_ios_bundle_flutter_assets
#0 _ProcessImpl._runAndWait (dart:io-patch/process_patch.dart:519:7)
#1 _runNonInteractiveProcessSync (dart:io-patch/process_patch.dart:686:18)
#2 Process.runSync (dart:io-patch/process_patch.dart:79:12)
#3 Context.runSyncProcess (file:///Users/local/flutter/packages/flutter_tools/bin/xcode_backend.dart:154:20)
#4 Context.runSync (file:///Users/local/flutter/packages/flutter_tools/bin/xcode_backend.dart:118:34)
#5 Context.buildApp (file:///Users/local/flutter/packages/flutter_tools/bin/xcode_backend.dart:539:34)
#6 Context.run (file:///Users/local/flutter/packages/flutter_tools/bin/xcode_backend.dart:51:9)
#7 main (file:///Users/local/flutter/packages/flutter_tools/bin/xcode_backend.dart:17:5)
#8 _delayEntrypointInvocation.<anonymous closure> (dart:isolate-patch/isolate_patch.dart:312:33)
#9 _RawReceivePort._handleMessage (dart:isolate-patch/isolate_patch.dart:193:12)
Command PhaseScriptExecution failed with a nonzero exit code
Any help here would be greatly appreciated.
Topic:
Developer Tools & Services
SubTopic:
Xcode Cloud
Tags:
Xcode
Signing Certificates
Xcode Cloud
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",
My post-build script takes the "developeridexport" archive export, zips it up and uses notarytool to notarize it. I then add the .zip to a .dmg disk image. The next step is to codesign the disk image before notarizing that too. The issue is my Developer ID Application certificate is not accessible to the build host. (When I was doing this in Microsoft AppCenter (now defunct), it had a copy of my Developer ID Application certificate.) What steps do I need to take to get the disk image signed for notarization?
Thanks!
Lance
Topic:
Developer Tools & Services
SubTopic:
Xcode Cloud
Tags:
Signing Certificates
Code Signing
Developer ID
I cannot setup a workflow - every time it says "This operation could not be completed" after granting access to the source code.
I removed the app from AppStore Connect, I logged out from Xcode, removed and reset the app from Github, initialized a new repository, reset Xcode Derived Data, reset the Profiles and Certificates.
I tried everything and nothing worked. Any help?
Xcode 26 RC is not available on Xcode Cloud. This is a serious blocker affecting developers trying to be on App Store on day 1 of the OS 26 release.
Is there an estimate when this can be in place?
I have now signed out of my account in Xcode, quit the application, signed back in, and also cleared the Xcode derived data and cache.
However, I am still receiving the 401 Unauthorized error
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 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)))
So my xcode cloud build have been stuck for 12 hours, is there something wrong with me or the service isnt working rn?
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
We would like to request an enhancement to Xcode Cloud workflows to support skipping builds when a GitHub Pull Request is in Draft state.
Our team frequently collaborates on pull requests that go through multiple iterations during the code review cycle. Each small commit or push triggers an Xcode Cloud workflow run, even if the PR is still in draft and not ready for final review or CI validation. This leads to:
Wasted compute resources and time on draft work that is not yet intended for integration.
Increased noise in Xcode Cloud logs and dashboards.
Longer feedback cycles for meaningful PRs, since draft workflows compete for available concurrency.
A simple option in the workflow configuration (e.g., “Skip runs for draft pull requests”) would address this problem by:
Reducing unnecessary workflow executions.
Freeing up capacity for production-ready and review-ready builds.
Improving overall developer productivity by aligning CI runs with the actual readiness of a PR.
This feature would be especially valuable for teams with frequent collaboration and long-lived PRs.
Thank you for considering this request—we believe it would significantly improve the efficiency of Xcode Cloud for real-world development workflows.