For some time now XCode Cloud build keep failing with: The step invocation hit a user timeout. The xcodebuild archive invocation timed out. No activity has been detected on stdout, stderr or the result bundle in 30 minutes. This happens specifically on Asset catalogs processing. In my case the app has like 8K images, with most of them tagged via Apple's ODR system so only the assets user needs are loaded, but the associated build step still takes a lot of time, usually 90+ minutes. It was fine before the timeout got implemented. Is there any whay to raise the timeout for a specific project? As it stands now the XCode Cloud is useless for this project as it can't do what it was intended for.

Archive a package. [Window] -> [Organizer] -> select package just archived -> click [Distribute App] select [App Store Connect] -> click [Distribute] -> CRASH! crash log Process: Xcode [12835] Path: /Applications/Xcode.app/Contents/MacOS/Xcode Identifier: com.apple.dt.Xcode Version: 15.3 (22618) Build Info: IDEApplication-22618000000000000~2 (15E204a) App Item ID: 497799835 App External ID: 863955376 Code Type: ARM-64 (Native) Parent Process: launchd [1] User ID: 501 Date/Time: 2024-04-15 11:05:05.6599 +0800 OS Version: macOS 14.4.1 (23E224) Report Version: 12 Anonymous UUID: E74ED973-D26C-0B5C-FDB1-837215F4F6B9 Sleep/Wake UUID: 6627EBDD-D3B7-4988-B9E5-BEDB5E1ED228 Time Awake Since Boot: 92000 seconds Time Since Wake: 11424 seconds System Integrity Protection: enabled Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Termination Reason: Namespace SIGNAL, Code 6 Abort trap: 6 Terminating Process: Xcode [12835] Application Specific Information: abort() called Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 libsystem_kernel.dylib 0x194e6aa60 __pthread_kill + 8 1 libsystem_pthread.dylib 0x194ea2c20 pthread_kill + 288 2 libsystem_c.dylib 0x194dafa20 abort + 180 3 libswiftCore.dylib 0x1a4f049f4 swift::fatalErrorv(unsigned int, char const*, char*) + 128 4 libswiftCore.dylib 0x1a4f04a14 swift::fatalError(unsigned int, char const*, ...) + 32 5 libswiftCore.dylib 0x1a4f04be0 swift::swift_abortRetainUnowned(void const*) + 48 6 libswiftCore.dylib 0x1a4f08f10 swift_unownedRetainStrong + 140 7 SwiftUI 0x1c1cea47c 0x1c075f000 + 22590588 8 SwiftUI 0x1c1cea42c 0x1c075f000 + 22590508 9 AppKit 0x198c517d4 -[_NSQuickActionAutovalidationScheduler windowDidUpdate:] + 140 10 CoreFoundation 0x194f76b1c __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 148 11 CoreFoundation 0x19500adb8 ___CFXRegistrationPost_block_invoke + 88 12 CoreFoundation 0x19500ad00 _CFXRegistrationPost + 440 13 CoreFoundation 0x194f45648 _CFXNotificationPost + 768 14 Foundation 0x196061464 -[NSNotificationCenter postNotificationName:object:userInfo:] + 88 15 CoreFoundation 0x194fadd4c -[NSArray makeObjectsPerformSelector:] + 212 16 AppKit 0x1987dccb4 -[NSApplication(NSWindowCache) _updateWindowsUsingCache] + 108 17 AppKit 0x1987dcc0c -[NSApplication updateWindows] + 64 18 AppKit 0x198c19a3c __38-[NSApplication setWindowsNeedUpdate:]_block_invoke_2 + 56 19 AppKit 0x198c1eb6c ___NSRunLoopObserverCreateWithHandler_block_invoke + 64 20 CoreFoundation 0x194f81254 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 36 21 CoreFoundation 0x194f81140 __CFRunLoopDoObservers + 536 22 CoreFoundation 0x194f8076c __CFRunLoopRun + 776 23 CoreFoundation 0x194f7fe0c CFRunLoopRunSpecific + 608 24 HIToolbox 0x19f71b000 RunCurrentEventLoopInMode + 292 25 HIToolbox 0x19f71ac90 ReceiveNextEventCommon + 220 26 HIToolbox 0x19f71ab94 _BlockUntilNextEventMatchingListInModeWithFilter + 76 27 AppKit 0x1987d8970 _DPSNextEvent + 660 28 AppKit 0x198fcadec -[NSApplication(NSEventRouting) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 700 29 DVTKit 0x10313f858 -[DVTApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 300 30 AppKit 0x1987cbcb8 -[NSApplication run] + 476 31 DVTKit 0x10313eb24 -[DVTApplication run] + 60 32 AppKit 0x1987a2f54 NSApplicationMain + 880 33 dyld 0x194b1a0e0 start + 2360

I'm getting a build error in Xcode Cloud when I'm trying to build my app. I've added visionOS support to my app and I'm getting a bunch of errors when it's trying to build the iOS version by the looks of it (archiving fails and spits out a bunch of missing asset errors for iOS)… I'm using alternative app icons on iOS… both my visionOS icon and iOS app icon use the same "AppIcon" name in the asset library… while my other alternative icons have separate naming and are only configured an iOS icons (there's no option to use them for visionOS currently)… I'm assuming it's something to do with iOS looking for or not finding my alternative icons for both the visionOS and iOS "AppIcon"? Missing Icon. The Info.plist key CFBundleIcons.CFBundleAlternateIcons contains an entry “green-icon” that references asset “green-icon.” No such asset is present in the asset catalog. Missing Icon. The Info.plist key CFBundleIcons.CFBundleAlternateIcons contains an entry “red-icon” that references asset “red-icon.” No such asset is present in the asset catalog. Missing Icon. The Info.plist key CFBundleIcons~ipad.CFBundleAlternateIcons contains an entry “white-icon” that references asset “white-icon.” No such asset is present in the asset catalog. Any ideas? Thanks!

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.

We had Xcode Cloud working with our project. We needed to re-auth the repo which failed and ended up needing to remove the config to reset it up as new. When on AppStoreConenct it shows its now not configured and to setup, which is good but when launch Xcode, press setup Xcode cloud it just gets stuck on loading source code repositories.

我构建了一个新的应用程序，还未发布到应用市场，只是提交了测试，前面都是正常的 但是今天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, 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?

Every time I try to build my Vision Pro app using Xcode Cloud, I get the error "Command compileSkybox failed with a nonzero exit code". I have even tried to build a completely empty project (settings: "Volume", "Reality Kit" and "Progressive") and I still get the error. When I build the project locally, there are no errors. Does anyone have any idea what the problem is?

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

My project has UI tests with total length of ~50 minutes. I'm using Xcode Cloud for builds delivery, UI tests execution is the part of the workflow. When I was using Monterey as tests environment everything was fine, but now it's no longer available so i had to switch to Sonoma. Since this i wasn't able to run anything but a couple of separate UI tests, when I run all of them I'm having 2 major issues. Locally on my machine I have the same Xcode/MacOS/simulator versions and everything works perfectly, issues only appear on Xcode Cloud. Here are they: There is a huge time gap between build-for-testing is finished and test-without-building is started. The gap is more than 1 hour so the sum of build time, ui tests time and the gap results in more than 2 hours and tests execution fails with the timeout. Funny is when I try to run the a single UI test or just run unit tests this gap only lasts for like 2-6 minutes, but when I add more tests the gap goes huge and fails everything. Also I guess my company is paying for those gaps and runs of tests when they timeout because of it even tho it's not our fault. Second issue is that some UI tests just freeze in the meddle of execution. This happens when UI tests is trying to interact with text fields on modal view controllers, sometimes it happens during the text field lookup, sometimes - after it takes focus and test is trying to type things into it. This is cannot be dodged anyhow and it is not related to some specific code - I've intentionaly rewritten the whole view controller from UIKit to SwiftUI , changed the way I present it and the location of presentation. Looks like just having a text field on a modal view is enough for test to freeze. Have anyone experienced something like this? Found any solutions?

[!] The Runner [Debug] target overrides the ENABLE_BITCODE build setting defined in `Pods/Target Support Files/Pods-Runner/Pods-Runner.debug.xcconfig'. This can lead to problems with the CocoaPods installation How to fix this error ?

Since the release of Xcode 15, my tests aren't functioning on Xcode Cloud. The login screen, which is a web view, isn't loading correctly during the Xcode Cloud UI tests, as depicted in the screenshot below: Any insights on what might be causing this error? We haven't made any changes to this feature, and it operates smoothly locally.

I can access my Build Workflows in Xcode via Report Navigator -> Cloud. I also used to see the builds on AppStoreConnect -> Select App/Framework -> Xcode Cloud Tab, but it has abruptly stopped working. I see an error message as below. 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 confirmed with my Developer Program Account Holder that they are also seeing the same error. Any suggestions to solve this?

Since today (and the release of the stable Xcode 15.3 to Xcode Cloud), release builds for visionOS are failing with following error: Unable to find a destination matching the provided destination specifier: { generic:1, platform:visionOS } ... { platform:visionOS, id:dvtdevice-DVTiOSDevicePlaceholder-xros:placeholder, name:Any visionOS Device, error:visionOS 1.1 is not installed. To use with Xcode, first download and install the platform } Yesterday the build worked with 15.3 RC (although I couldn't release it because the RC wasn't the newest one and RC2 hasn't been added to Xcode Cloud). Has anybody found a solution or is it something, Apple has to fix?

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.