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?
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
Hi, recently something happened in Xcode Cloud, and the build times increased massively. In our CI workflow we run test, and one of the phases executes xcodebuild build-for-testing: the duration of this phase moved from about 8 minutes to about 36 minutes, without any major changes on our side.
We observed this:
in different apps;
even when running a build on a old tag.
All other phases don't seem affected, it's just the xcodebuild build-for-testing phase.
I'm attaching 2 screenshots of the logs from AppStoreConnect that show the duration of each phase, where build 7600 is older and 7700 is more recent (but was run on a tag from a few weeks ago, to exclude issues related with the code base itself).
We had not other option than to disable the CI checks for PRs, because they would take too long, and use up too much of Xcode Cloud time.
What's happening?
Thanks
Topic:
Developer Tools & Services
SubTopic:
Xcode Cloud
We have a cross platform app that we build with Xcode Cloud and distribute via TestFlight.
We want to test builds with the Xcode Beta. So we have the following build environment:
Xcode version: Xcode 16 beta 6 (16A5230g)
macOS Version: macOS Sonoma 14.5 (23F79)
Everything builds and submits to TestFlight fine. The App runs fine on iOS 18 beta and macOS 15 beta. But when attempting to install via TestFlight and launch the App on macOS 14..6.1 it crashes immediately with what appears to be a missing Foundation symbol.
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Termination Reason: Namespace DYLD, Code 4 Symbol missing
Symbol not found: _$s10Foundation14NSDecimalRoundyySpySo0B0aG_SPyADGSiSo14NSRoundingModeVtF
Referenced from: <CBEBC813-C7B6-3D8E-BE62-16F2EFFEB1FE> /Applications/MyApp.app/Contents/MacOS/MyApp
Expected in: <2F87A303-430F-3EA5-9492-3033F4FEE64B> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
(terminated at launch; ignore backtrace)
Thread 0 Crashed:
0 dyld 0x7ff8139f687a __abort_with_payload + 10
1 dyld 0x7ff813a0f7f7 abort_with_payload_wrapper_internal + 82
2 dyld 0x7ff813a0f829 abort_with_payload + 9
3 dyld 0x7ff81399c2b5 dyld4::halt(char const*, dyld4::StructuredError const*) + 335
4 dyld 0x7ff8139994bd dyld4::prepare(dyld4::APIs&, dyld3::MachOAnalyzer const*) + 4099
5 dyld 0x7ff8139982e4 start + 1812
Is it expected that this should work? Is this a known issue? Is there any workaround for it?
Should I file feedback or a DTS?
Hello everyone! I found that the Xcode Cloud workflows under my project are completely stuck. The tasks that are already running cannot be completed. Newly started tasks remain in the queued state forever and cannot be canceled. They are consuming my usage quota 😢. Has anyone else encountered the same issue?
I am setting up a new app and am having problems with Xcode Cloud. From Xcode if I click on the "Cloud" button under the Report Navigator I get a spinner for a long time then get the message "Could not load Xcode Cloud data". I also visited the "Xcode Cloud" tab under my app in App Store Connect and I get a spinner and nothing loads.
This is a recent account and I'm setting up Xcode Cloud for the first time. Below is what I've tried and I'm out of ideas on how to get this working.
In Xcode, I signed out and back in as the Account Holder
Closed Xcode and reopened
This occurred yesterday and today and have not seen a problem under the Apple System Status page
On the latest Xcode 16.2
Checked the Signing & Capabilities tab in Xcode and my team a bundle Id is correct and it's happy with signing. At this time on my machine I am using the distribution profile.
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?
My team's Xcode Cloud build started timing out when we recently upgraded to Xcode 16.0.0. Specifically, the test build phase times out due to exceeding the 2 hour limit.
The Test - iOS action could not complete due to an error. The error may not occur on rebuild.
Build has exceeded the maximum allotted time. Each build can run for up to 120 minutes. If a build has not yet finished at this time, all incomplete actions will be cancelled.
When running Xcode 15.4.0, the test build phase completed in roughly 45 minutes.
It's also important to know that our test build completes in about 15 minutes when executing on one of our in-house Mac mini build machines (Apple Silicon). So the issue seems to be with Xcode Cloud + Xcode 16.0.0 and not our project.
We have been burning through Xcode Cloud hours hoping that at some point Xcode Cloud will be fixed.
The status page right now is all "green":
https://developer.apple.com/system-status/
Is there a known issue with Xcode Cloud + running tests? We have combed through our project's Xcode Cloud logs and artifacts, but nothing jumps out as something on our end.
Also, there is a large file named "Test Products for ", but we can't download it due to crashes/ errors:
The Xcode IDE UI shows this file as 1.99GB
Xcode crashes when attempting to download the file.
The App Store Connect UI shows this file as ~1GB (possibly just omitting precision).
An error response page is returned when attempting to download.
Thanks in advance for any advice/ feedback.
Topic:
Developer Tools & Services
SubTopic:
Xcode Cloud
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 !
Topic:
Developer Tools & Services
SubTopic:
Xcode Cloud
Tags:
Swift Packages
Continuous Integration
Xcode Cloud
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'm running on xcode 16, the project archives just fine on the local machine. However, with xcodecloud. It's running into exist code 70 on the following command
xcodebuild -exportArchive -archivePath .....
#output
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
There was an updated tonight I assume to something and now I am getting this for all firebase modules when I push to App Store connect "Invalid sdk value. The value provided for the sdk portion of LC_BUILD_VERSION in proxie2.app/Frameworks/GoogleAppMeasurementIdentitySupport.framework/GoogleAppMeasurementIdentitySupport is 18.2 which is greater than the maximum allowed value of 18.1." now even when I revert back to suer old firebase packages I get the same errors no matter what please fix this asap...
I am experiencing a lot of problems with Xcode Cloud in last days. I can't hardly login, refresh time is so high, showing blank pages or not found all the time. Anyone else is experiencing the same?
Hello, when I open the "Cloud" tab in the Report navigator, it shows "Failed to analyze workspace" and I cannot do anything. I can't start a build, nor can I manage or create workflows. All options are greyed out.
When loading the project, in Console I see the following errors from Xcode:
fault 11:07:19.805349+0100 Xcode ❌❌❌ Assertion failure #0 in <private>
error 11:07:19.816641+0100 Xcode ❌❌❌ Assertion backtrace: >><private>0 XcodeCloudKit 0x00000001195309d8 $s13XcodeCloudKit17AssertionHandlingPAAE16logFullBacktraceyyFAA0D0O7HandlerV_Tg5Tf4d_n + 48
1 XcodeCloudKit 0x00000001192583c4 $s13XcodeCloudKit26ShellBasedProjectDescriberPAAE17describePublishery7Combine03AnyI0Vy6OutputQzs5Error_pG5InputQzFAKs5Int32V_10Foundation4DataVARtcfU_AA021AllArchivableProductsdG0V_Tg5 + 2012
2 XcodeCloudKit 0x000000011925ec90 $ss5Int32V10Foundation4DataVAE7Combine12AnyPublisherVy6Output13XcodeCloudKit26ShellBasedProjectDescriberPQzs5Error_pGIegyggo_AB8exitCode_AE6stdoutAE6stderrtAOIegnr_AjKRzlTRAJ021AllArchivableProductskN0V_TG5TA + 40
3 Combine 0x00000001a072351c $s7Combine10PublishersO7FlatMapV5Outer33_E91C3F00A6DFAAFEA2009FAF507AE039LLC7receiveyAA11SubscribersO6DemandV6OutputQy_F + 300
4 Combine 0x00000001a0725128 $s7Combine10PublishersO7FlatMapV5Outer33_E91C3F00A6DFAAFEA2<…>
<<
fault 11:07:19.822299+0100 Xcode ❌❌❌ Assertion failure #0 in <private>
fault 11:07:19.822405+0100 Xcode ❌❌❌ Assertion failure #0 in <private>
error 11:07:19.824577+0100 Xcode ❌❌❌ Assertion backtrace: >><private>0 XcodeCloudKit 0x00000001195309d8 $s13XcodeCloudKit17AssertionHandlingPAAE16logFullBacktraceyyFAA0D0O7HandlerV_Tg5Tf4d_n + 48
1 XcodeCloudKit 0x00000001195e088c $s13XcodeCloudKit17DiscoveredProductO16DescriptorsCacheC13updatePlanner11environmentyAA21DeploymentEnvironmentO_tFys6ResultOySayAC0E10DescriptorVGs5Error_pGcfU_ + 740
2 XcodeCloudKit 0x0000000119289fa8 $s7Combine9PublisherP13XcodeCloudKitE18sinkAtMostOneValue4file4line6resultAA14AnyCancellableCs12StaticStringV_Suys6ResultOy6OutputQzs5Error_pGctFyAA11SubscribersO10CompletionOy_sAQ_pGcfU0_AA0nB0VySay0cD3API10ComponentsO7SchemasO13BuildArtifactVGsAQ_pG_Tg5Tm + 68
3 XcodeCloudKit 0x00000001192a1ef4 $s7Combine9PublisherP13XcodeCloudKitE18sinkAtMostOneValue4file4line6resultAA14AnyCancellableCs12StaticStringV_Suys6ResultOy6OutputQzs5Error_pGctFyAA11SubscribersO10CompletionOy_sAQ_pGcfU0_AA0nB0VySay0cD3API10ComponentsO7Sc<…>
<<
Obtained by filtering by xcode-cloud-assertion category.
Is there anything I can do to fix this? Thanks!
Hi,
I'm trying to register the application with Xcode Cloud.
For that, I click on the "cloud" button in Xcode.
First steps goes OK, but it fails at "create App on App Store Connect"
The error is Cannot register the product
Usually, I change the bundle name, but this time it gets weird, as Xcode managed to create the Identifier, as it is not taken.
So the identifier is created in the developer portal but it fails anyway.
I also tried to create the app directly in the portal, and it works, therefore the app name is not the problem.
Then I delete the app and try again with Xcode and it fails...
Any solution for this issue please?
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!
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
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.
I have checked that my scheme is shared and I do in fact have the scheme in my xcode project. But whenever I try to run Xcode cloud, it fails with the message that "A scheme named 'MyAppScheme' does not exist in MyAppProject.xcodeproj"
Any tips on what I could be doing wrong?
Lost access to all the build artifacts in Xcode Cloud.
When I try downloading any build artifact from the web page I'm getting:
{"message":"You are not authorized to access this team’s resources."}
Same attempt from Xcode just crashes the app.
Started to happen today or some time yesterday, after 12am EST.
I just discovered that I can no longer download any artifacts from Xcode Cloud, whether from newly built workflows or previous ones. When I try to download in Xcode, it crashes immediately. When downloading from App Store Connect, it redirects to an HTML page with the following content.
{"message":"You are not authorized to access this team’s resources."}
I've already tried re-logging into my Apple account. Is anyone else experiencing the same issue?