I finally signed up for Xcode cloud, but it doesn't work after successful GitHub app installation. 401 in the console for: https://appstoreconnect.apple.com/olympus/v1/providerSwitchRequests I tried multiple things, even wrote to apple. Is it only for payed GitHub users? I have a free private repo. Hope someone has an idea. This is the error message when I give Xcode Cloud access to all repositories: Die Verbindung von Xcode Cloud mit deinem Quellcodeverwaltungsanbieter konnte nicht erstellt werden. Translation: The connection from Xcode Cloud to your source code management provider could not be established.

Hello! I'm having difficulties getting Xcode Cloud to see new changes to my files in my project that are being pushed. Previously, this was due to some network situation on my GitLab self-hosted server. This has likely been changed but I'm having difficulties because I tried to use an integration in GitLab for App Store Connect which isn't the same as Xcode Cloud and so as a result it didn't work. I tried starting over and setting up the system from scratch but the web hook hasn't appeared as it had done the first time I set it up. Does anyone know how to set up the web hook manually for Xcode Cloud so that Xcode Cloud is notified when a new push and other relevant events occur in my repository? The web hook that was previously there would error when I tried testing it on the GitLab end, but since I had deleted it, the web hook is not longer present and I was unable to recreate it as part of the setup procedure because it was pretty opaque to me the first time around and I followed the procedure in the documentation to get it to work. Xcode Cloud works fine when I manually start a build.

This issue started to appear in the last couple of weeks. And it's annoying because Xcode Cloud actually is based on build duration. Here is a sample: The whole build took like 10 minutes. We can easily consume the 25 hours free tier because of these. The crash logs are completely useless. And the failing tests change from one run to the other and on different simulators. I really hope Xcode Cloud team look into this as it's frustrating and kills the whole point of Xcode Cloud (BTW, these issues won't happen on Bitrise).

My UI Tests are not running on Xcode Cloud CI pipeline, they run fine on locally. they seem to be timing out due to the application not running in the pipeline and I have tried everything I could to fix it yet nothing. The error I see is : Failed to application com.xyz.app is not running

Every time I try to build archive iOS app I get error like this: Type 'ImageResource' has no member <<resource_name>>. I am using generated ImageResource through out my app. I can archive and upload build using Xcode. But it is not working using Xcode Cloud.

Xcode Cloud reports the following error A scheme called PlatoSafe does not exist in Plato.xcodeproj However, my project only has one scheme named Plato. I search the proj using git grep PlatoSafe and don't see such a name anywhere. I do xcodebuild -list, and the output shows Plato as the only scheme. Where does Xcode Cloud get the scheme name PlatoSafe from?

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

I started to use Xcode Cloud recently trying to understand how the whole build process etc. works. I created some workflows, integrated ci scripts to let fastlane create snapshots in the end, and everything seem to work while I was making progress step by step to get it up and running (struggling with the environment, etc.). Then last night it suddenly stopped working in the form, that Xcode shows the builds, but the last build still shows a spinner, although the job has finished already When I try to cancel the last run from Xcode (thought it was not finished) I get an error: Failed to Cancel Build 57. An internal error occurred while authenticating. Try again later. (FB13802231) When I open Manage Workflows…, Xcode suddenly shows "This operation could not be completed" and details reveal: The operation couldn’t be completed. ((extension in XcodeCloudKit):XcodeCloudAPI.Client.HTTPClientError error 0.) (FB13802952) Trying to access the Xcode Cloud tab of the app or general from users and permissions shows a white page with a spinner. The console filtered by Xcode shows (around the time the error happens): Failed to query public key: 0xe800000c The Safari browser console shows: An internal error occurred while authenticating. Try again later. What works: I can login to AppStore Connect without problem. I am logged-in in Xcode (but there's no option to logout and re-login) I can use tools like fastlane with API calls (or some xcc command line tool) and list the products, workflows and runs using my API key. From this information I also figured out, that the build in question (57) where Xcode still shows the spinner, has finished (failing) already. I was also able to start a new build manually (58) via API, which however has finished 3 seconds after creation, but has never started (startedDate is empty while createdDate and finshedDate contains data). I was able to delete the workflow via API in hope that the problem goes away, but theres no change in Xcode (still shows the same picture with the workflow and last build 57 spinning). I should have used <4 / 25 hours of free plan of Xcode Cloud this month, so limit not exceeded. I'm on macOS 14.4.1, Xcode 15.3. Seems I can't make use of Xcode Cloud at all anymore right now which keeps me from proceeding now on my way to first time deliver to AppStore (still understanding and learning). I also provided info about the 2 Xcode errors as feedback, which I linked above. Any help on how to reset / do whatever is necessary to make it work again is very much appreciated.

Hi everyone, I'm encountering an intermittent issue with my Xcode Cloud CI/CD pipeline when pulling Swift Package Manager (SPM) dependencies from AWS CodeArtifact. The build process occasionally fails with an SSL error, but other times it succeeds without any issues. This inconsistency is causing significant disruption to our continuous integration process. Environment: Xcode Cloud Swift Package Manager (SPM) for dependency management AWS CodeArtifact as the package registry Error Message: Error: registry login using https://xx-xx-xx.codeartifact.eu-central-1.amazonaws.com/swift/***/login failed: The certificate for this server is invalid. You might be connecting to a server that is pretending to be "xx-xx-xx.codeartifact.eu-central-1.amazonaws.com" which could put your confidential information at risk.. Would you like to connect to the server anyway?

I'm trying to increase the compute hours on our Xcode Cloud, but it says this needs to be performed via the Apple Developer App. The issue is that my iOS devices are authenticated with my personal Apple ID and not my work/developer Apple ID. Is there any way to upgrade my subscription on Desktop? Any other suggestions how I can upgrade our subscription?

We have a release build workflow for our primary app, and we set up email and webhook notifications for it. This is to hopefully not miss when this workflow completes. Unfortunately, we seem to be getting these build notifications days after completion. This has happened several times. In this case, the build completed Friday afternoon for us, we submitted the new version, and it was released hours later. But we didn't get the workflow notification until Sunday. We get them in Slack and Email. I'm considering turning these notifications off since their late arrival is rendering them almost useless.

After archiving no artifacts could be found but the release is in the Testflight, it has been happening since this morning. Do you have any ideas about how can I solve it? Thanks. @eskimo @meaton Update: The 501 (Not Implemented) status code indicates that the server does not support the functionality required to fulfill the request

can not login successfully, if I input my password it will give my error hint. but when I type the right password and username, nothing happened, the cloud tab still appear like the one in the screenshot . I have already to to restart xcode, It do not help. the same usename and password can login into the forum app store connect. what should I do?

Since April 30 (yesterday as of this writing) Xcode Cloud builds are failing randomly, usually citing an internal Apple network failure. NSLocalizedDescription=Communication with Apple failed, NSLocalizedRecoverySuggestion=A non-HTTP 200 response was received (502) for URL https://developerservices2.apple.com/services/QH65B2/listTeams.action?clientId=XABBG36SBA Because of this network failure, the build cannot fetch my app ID NSLocalizedDescription=Capabilities for bundle ID "Twine" could not be fetched. Please file a bug report at https://feedbackassistant.apple.com and include the Update Signing report from the Report navigator., IDEDistributionIssueSeverity=3 This is a multi platform app, iOS, macOS, and visionOS. Usually one or two platforms will succeed, with one or two failing. From build to build, with no source changes, the successful platform randomly changes. But I never get a complete build.

During SPM Package resolution we are seeing lots of 502 errors in the logs when Xcode Cloud tries to talk to github. Anyone else seeing this? Not sure how to get this issue resolved but it is impacted all of our builds. Example of the error we're seeing. We see these for lots of different packages and even our own source (though in that case it looks like Xcode Cloud tried again and succeeded the second time). xcodebuild: error: Could not resolve package dependencies: Failed to clone repository https://github.com/zendesk/sdk_zendesk_ios: Cloning into bare repository '/Volumes/workspace/DerivedData/SourcePackages/repositories/sdk_zendesk_ios-1d7ac730'... error: RPC failed; HTTP 502 curl 22 The requested URL returned error: 502 fatal: expected flush after ref listing Failed to clone repository https://github.com/apple/swift-async-algorithms: Cloning into bare repository '/Volumes/workspace/DerivedData/SourcePackages/repositories/swift-async-algorithms-c3a8d752'... fatal: unable to access 'http://github.com/apple/swift-async-algorithms/': The requested URL returned error: 502

Today I have tried to add a second archive action for visionOS. I had added a visionOS destination to my app target a while back and can build and archive my app for visionOS in Xcode 15.3 locally, and also run it on the device. Xcode Cloud is giving me the following errors in the Archive - visionOS action (Archive - iOS works): Invalid Info.plist value. The value for the key 'DTPlatformName' in bundle MyApp.app is invalid. Invalid sdk value. The value provided for the sdk portion of LC_BUILD_VERSION in MyApp.app/MyApp is 17.4 which is greater than the maximum allowed value of 1.2. This bundle is invalid. The value provided for the key MinimumOSVersion '17.0' is not acceptable. Type Mismatch. The value for the Info.plist key CFBundleIcons.CFBundlePrimaryIcon is not of the required type for that key. See the Information Property List Key Reference at https://developer.apple.com/library/ios/documentation/general/Reference/InfoPlistKeyReference/Introduction/Introduction.html#//apple_ref/doc/uid/TP40009248-SW1 All 4 errors are annotated with "Prepare Build for App Store Connect" and I get them for both "TestFlight (Internal Testing Only)" and "TestFlight and App Store" deployment preparation options. I have tried to remove the visionOS destination and add it back, but this is not changing the project at all. Any ideas what I am missing?

I'm trying to generate a build using Xcode Cloud, but the error below is displayed: /bin/sh: /Volumes/workspace/repository/ios/Pods/../../node_modules/react-native/ReactCommon/../scripts/xcode/with-environment.sh: No such file or directory This error occurs when I'm generating the archive. It's worth mentioning that if I try to run the archive manually in Xcode > Product > Archive, it works. Can someone help me out?

Hi, I’m using the snapshot testing library from https://github.com/pointfreeco/swift-snapshot-testing I recorded the snapshot tests on the iPhone 15 pro simulator on iOS 17.4 and Xcode 15.3 On my M1 Max MacBook Pro Within the tests found in https://github.com/fespinoza/sample-json-app/blob/84b81ee3fa1d24e97bbeded65487b32258a42325/SampleProjectTests/MovieDetails/MovieDetailsViewTests.swift I try to control all the traits and properties I can, to make sure the test is run in the same environment in Xcode Cloud For some reason though, on Xcode Cloud, Text with multiline strings have a different line height than on my machine and thus the test fail I don’t understand: why that happens how to debug this situation Does anyone here have any pointers? Reference Image From my machine Failure Image from Xcode Cloud P.S. thread initially posted in https://github.com/pointfreeco/swift-snapshot-testing/discussions/842 but i haven’t gotten any answers, trying here instead

Hello guys, I've been dealing with one error in my xcode cloud configuration. I want to auto-deploy the app version to Testflight on something is merged to main branch. Of course if I do at my local environment it works perfect. But when I try to execute it at XCode Cloud I've got this error. I really don't have any idea about how to fix it. Thanks a lot for your time 😊 Invalid Signature. The main app bundle SyncTion at path SyncTion.app has following signing error(s): valid on disk SyncTion.app: does not satisfy its designated Requirement SyncTion.app: explicit requirement satisfied . Refer to the Code Signing and Application Sandboxing Guide at http://developer.apple.com/library/mac/#documentation/Security/Conceptual/CodeSigningGuide/AboutCS/AboutCS.html and Technical Note 2206 at https://developer.apple.com/library/mac/technotes/tn2206/_index.html for more information.

我构建了一个新的应用程序，还未发布到应用市场，只是提交了测试，前面都是正常的 但是今天TestFlight提审时提示“你的请求无法完成请稍后再试” 内部测试包能上传，但是测试机下载测试时提示“所请求的应用不存在或不可用” 有哪位大大能帮忙解决么？急急急····