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提审时提示“你的请求无法完成请稍后再试” 内部测试包能上传，但是测试机下载测试时提示“所请求的应用不存在或不可用” 有哪位大大能帮忙解决么？急急急····

I've been running into problems when building on Xcode cloud. I keep getting errors with regards to PrivacyInfo.xcprivacy: No such file or directory. I'm not sure what the next steps are, as I originally built with only three errors: Then I attempted to pod install and pod update, and even tried to alter the target membership, but that only had me get more errors: I've looked at some of the other questions and responses in the forum about this issue, but none of them seemed to fix the No such file or directory issue. Any advice would be appreciated. Thanks!

Hi, I tried to put in place a workflow to automatically generate API data model using Swagger-Codegen on Xcode Cloud. In the ci_pre_xcodebuild.sh we install swagger-codegen using brew. But installation fails due to uninstalled Apple Command Line Tools. Error: python @3.12: the bottle needs the Apple Command Line Tools to be installed. Any thoughts about this ? Regards,

Hi, We've been using Xcode cloud for one of our apps without issues for a while now. We're happy with it, and want to use it to build and publish all the apps we manage. But these past few days i've tried to set up a new app without success. I'm receiving the errors Invalid Signature. Code failed to satisfy specified code requirement(s). The file at path “{app}/Frameworks/hermes.framework/hermes” 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. Invalid Signature. Code failed to satisfy specified code requirement(s). The file at path “{app.app}/{app}” 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 errors seems aimed towards someone trying to build locally, as to my understanding, i can't affect the cloud signing used by the pipeline. Nonetheless, I've been trying to fix these by: Creating new certificates(both personal, and removing the xcode cloud ones) Deleting Xcode cloud data and starting over Changing, and testing, all relevant signing settings in project.pbxproj Testing various Xcode and MacOS versions in the config Creating provisioning profiles and specifying them in project.pbxproj Compared files and structures between a working project and this one Gone through all troubleshooting documentation and relevant posts and answers on various forums The issue only exists in Xcode cloud, and as far i can see there should be no issues with the servers. If i switch to the exact build, build it locally and publish it, there's no issue. Is there any more alternatives i can try before moving on from Xcode cloud to another solution?

Probably a long shot, but is there any way to use Xcode Cloud if I don't use any of the "big three" Git providers? My source control is Git, but it's provided by a tiny little startup called "Microsoft," (Azure Devops) and there doesn't seem to be any sort of manual config I can set up to give Xcode cloud access to it...

When running a SwiftUI Multiplatform app in Xcode Cloud I'm getting the following error: CIWatcher encountered an error in CIWatcherTests failed with: Failed to install or launch the test runner. (Underlying Error: Could not launch “CIWatcherTests”. Runningboard has returned error 5. Please check the system logs for the underlying cause of the error. (Underlying Error: The operation couldn’t be completed. Launch failed. (Underlying Error: Launchd job spawn failed))) This runs fine on iOS and all those tests pass. The SwiftUI app on Mac is a menu bar app so I'm not sure if this could be the issue as it's not launching for some reason on the Xcode Cloud system? Maybe I need to add some run option to make this work? When run locally both iOS and macOS pass all the tests successfully

Hello all! Since past Thursday, using this cURL: curl -X POST \ 'https://api.appstoreconnect.apple.com/v1/ciBuildRuns' \ --header 'Accept: */*' \ --header 'User-Agent: Thunder Client (https://www.thunderclient.com)' \ --header 'Authorization: Bearer XXXX' \ --header 'Content-Type: application/json' \ --data-raw '{ "data": { "type": "ciBuildRuns", "attributes": {}, "relationships": { "workflow": { "data": { "type": "ciWorkflows", "id": "NNNN" } }, "sourceBranchOrTag": { "data": { "type": "scmGitReferences", "id": "NNNN" } } } } } Of course, I removed the sensible information from my sample. This is the response: { "errors": [ { "status": "500", "code": "UNEXPECTED_ERROR", "title": "An unexpected error occurred.", "detail": "An unexpected error occurred on the server side. If this issue continues, contact us at https://developer.apple.com/contact/." } ] } I have written to Apple Support twice since they assure me that I will have a response in 2 working days, but I have not had any response. The rest of the API calls work correctly.

The available environment variables have this: CI_BRANCH The name of the source branch that Xcode Cloud checked out for the current build, for example, main. However, this is only available for builds started by a branch change. I tried using it in a manual build, and it was just an empty string. Is there a way to get the branch name for manually started workflows? You have to choose a branch to start one, so I'd assume that info is available somewhere.

Hi , 'MobileRTCScreenShare/MobileRTCScreenShareService.h' file not found during xcode cloud build , but when i run on local its working fine , please suggest the right way to solve the problem

We added a unit test workflow to Xcode Cloud and the step to generate the test report takes a whopping 20 minutes. We have a few thousand tests but the entire run was 28 minutes—is this expected? Locally, running the test suite (on m1) runs in about 2 minutes.

Hello! I'd love to be able to use Xcode Cloud, but I can't figure out how to make it fast enough. For example a build (from clean) that takes 30s on my M1 MacBook Pro takes 120s on Xcode Cloud. I looked at the build timelines for both local builds and cloud builds, and there is no apparent bottleneck on the cloud build. It appears to be compiling 10 to 12 files in parallel just like my local machine, just 4x slower. I'm on the free tier right now. Is it faster on the paid tiers?

I have a crash in my app that occurs during a test - but only when running on Xcode Cloud - locally tests always pass fine. I have a crash report that looks like the one below. I understand that abort is being called and includes an abort_message which I could normally see in the console if the debugger was attached, but as this is Xcode Cloud, is there any way where I can actually see this abort message? Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Termination Reason: SIGNAL 6 Abort trap: 6 Triggered by Thread: 0 Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 libsystem_kernel.dylib 0x10cb497a2 __pthread_kill + 10 1 libsystem_pthread.dylib 0x10cad4f30 pthread_kill + 262 2 libsystem_c.dylib 0x7ff80014cd30 abort + 133 3 libc++abi.dylib 0x7ff8002961b2 abort_message + 241 4 libc++abi.dylib 0x7ff80028838a demangling_terminate_handler() + 266 5 libobjc.A.dylib 0x7ff80004266e _objc_terminate() + 104 6 libc++abi.dylib 0x7ff80029560b std::__terminate(void (*)()) + 6 7 libc++abi.dylib 0x7ff800298024 __cxa_rethrow + 100 8 libobjc.A.dylib 0x7ff800063a71 objc_exception_rethrow + 37 9 CoreFoundation 0x7ff8003f1a32 CFRunLoopRunSpecific + 738 10 GraphicsServices 0x7ff80fe9d08f GSEventRunModal + 137 11 UIKitCore 0x7ff805bbb53d -[UIApplication _run] + 972 12 UIKitCore 0x7ff805bbffab UIApplicationMain + 123 13 SwiftUI 0x7ff84ab8aeda 0x7ff849b47000 + 17055450 14 SwiftUI 0x7ff84ab8ad93 0x7ff849b47000 + 17055123 15 SwiftUI 0x7ff84a82b0d7 0x7ff849b47000 + 13517015