Hello, Im trying to add my project to Xcode Cloud. Not first time. Now I'm getting this error: "To create a Xcode Cloud workflow, first add a remote source code repository from BitBucket, GitHub, or GitLab." Of course this project has origin (GitHub) and I'm using it with Xcode actively. Xcode 16.0, iOS app target 17.6. Sonoma - latest. What am I 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.

There seems to be a problem to a specific Apple Developer Account regarding Xcode Cloud Distribution (Signing). The Xcode Cloud Error Invalid Signature. Code failed to satisfy specified code requirement(s). The file at path “XcodeCloudTest.app/XcodeCloudTest” 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. Investigation Apple Developer Forums This issue seems to be known: https://developer.apple.com/forums/thread/746210 Debugging by ourselves We setup an example Xcode project from a default iOS Xcode app template to rule out any project issues. This example project failed with the same error as stated above. In the next step we tried the same example project with a different Apple Developer Account and it successfully distributed the example App through Xcode Cloud. Conclusion It seems like there is no setup issue on developer-side, because our example project works out-of-the-box on a different Apple Developer Account. Our only hope is that Apple will have a look on our Developer Account. Maybe there is some internal setting.

I've noticed that when using the Test action in an Xcode Cloud workflow, the xcodebuild command includes COMPILER_INDEX_STORE_ENABLE=NO while performing build-for-testing. This disables the index store, which is required by tools like Periphery to analyze unused code. Without indexing, Periphery triggers a fresh build internally, resulting in a significant increase in CI build time. Is there any way to enable indexing (COMPILER_INDEX_STORE_ENABLE=YES) on Xcode Cloud? Or alternatively, is there a recommended workaround to generate and access the index store? Any help is appreciated.

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?

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

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?

We have had 2 Builds so far stuck archiving. Both indicate in their logs that Build Archive took a normal amount of time (9m and 19m) but the step Archive - iOS never finished. One of them ran for more than 6 days until we noticed and canceled it. The other one ran for 18 hours, and also had to be canceled manually. They were in two different projects, with no significant changes. The first build ran on Xcode 16.4 (16F6) and macOS Sequoia 15.6 (24G84), which we had had no issues like this with until just now, and the second ran on Xcode 26 (17A324) and macOS Tahoe 26 (25A354). We tested our app on the newest Xcode version and had no issues. Submitted report using feedback assistant: FB20279737.

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?

Hi I am trying to integrate Xcode Cloud in our project but always getting This operation could not be completed error on Grant Access to Your Source Code screen. Upon send a feedback got to know that there is a API failure with status code 403. please help in resolving this Thanks

When testing on Xcode Cloud I am unable to use any simulators between iOS 16.2 and 17.5. I'm glad that there are options for <= 16.1, but given how small those userbases must be at this point it feels rather odd. Similarly, iOS 18 is still very new so it also has a disproportionately small number of users on it. Does not seem to matter if explicitly selecting Xcode/macOS versions. Am I configuring something incorrectly? Picked something wrong on a dropdown, checked the wrong box when setting up the workflow? Xcode 15.4 allows building to iOS 17.5, but not iOS 18. 🙃

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

I added a new target for macOS to my existing iPhone app. The new target ran successfully in Xcode. However, when I committed the changes, Xcode Cloud generated the error. I don't know what the error means. Would someone please give me a pointer? Thank you.

Issue Description The current Xcode Cloud webhook functionality requires developers to expose a public URL to receive webhook events, which poses a challenge in environments with security restrictions or limited network accessibility. Many developers need to receive webhook events locally without exposing their servers to the public internet. Proposed Solution A feature similar to Slack’s "Socket Mode" would allow developers to receive webhook events over a WebSocket connection without exposing a public URL. This socket-based solution could offer a more secure, streamlined, and accessible way for developers to work with webhooks, especially in closed network environments.

Hi, Our team uses Xcode Cloud to run unit tests, and since around November, we’ve been frequently experiencing timeouts with the following type of process: @Test func hogeTest() async { // do something hoge.do() // wait until done await wait(condition: { hoge.isDone }) // test result #expect(hoge.isSucceeded) } private func wait(condition: () async -> Bool, timeout: TimeInterval = 0.5, pollingInterval: TimeInterval = 0.01) async throws { let deadline = Date().addingTimeInterval(timeout) while Date() < deadline { if await condition() { return } try await Task.sleep(nanoseconds: UInt64(round(pollingInterval * TimeInterval(NSEC_PER_SEC)))) } Issue.record("timeout") } Although sleep is supposed to wait for only a few milliseconds, there are cases where it takes more than 10 seconds, leading to a timeout. What could be causing this instability in the sleep duration? Additionally, if there are other recommended ways to implement polling and waiting in Swift Testing, I would appreciate it if you could share them. A feedback report (FB15899163) has already been submitted. Best regards,

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

My builds failed today with 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. The thing is, I have Xcode Cloud configured to use the latest release. There is a separate configuration for "Latest beta or release", so why is it using the Xcode 16.2 Beta 3 build? This is clearly a beta. If you're going to give me an option to use the latest release, then it should do what it says.

Issue Description I'm have Local Swift Package which contains binary target to private github releases url is formed like below: https://api.github.com/repo/{owner}/{repo}/releases/assets/{asset_id}.zip I register the private repo to the xcodecloud, but still xcodecloud does not recognize "api.github.com" domain. So build keeps fails at downloading binary artifact. https://github.com/{owner}/{repo}/releases/download/{tag}/Myframework.xcframework.zip is not a valid choice since this kind of url, is not supported for private repository. Proposed Solution Please add authorization to the "api.github.com" like normal "github.com".

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 !

I have set the deployment target to iOS17.0 on all targets. Archiving and test works fine, but External testing fails?