build disappears

Same issue here. I've been trying to build a new version with xcode cloud since last night (14 hours ago). They all get stuck at 93%. I've tried with a fresh branch, retried existing builds, nothing seems to work. The changes seems minimal (just some small UI things). It really seems like xcode cloud is having issues, but nothing is reported on the xcode cloud status page.

We're not using Xcode Cloud but our TestFlight builds are also stuck in Processing - case ID 102802395012

We experience similar issue with all our apps: builds stuck in Processing status for the last 15+ hours

Same here, I have m app in Processing, only 118mb the file uploaded in the app. Had previous successful builds and even app live on iOS. I submitted a ticket in the Feedback Assistance (FB21625078). Please help

I figured out a workaround: Add a new “Copy Files” build phase to the target with the destination “Frameworks” with the following file /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift-6.2/macosx/libswiftCompatibilitySpan.dylib That is, copying the libswiftCompatibilitySpan.dylib file manually into the “Frameworks” directory of the bundle. The bundle now loads on older OS versions like macOS 15. However, this workaround is not a good solution as it requires me to manually find the libswiftCompatibilitySpan.dylib file and ensure to keep its path updated in the Xcode project settings each time the toolchain is updated. Ideally, Xcode would recognize that libswiftCompatibilitySpan.dylib is linked using rpath and include the file in the “Frameworks” directory automatically. Maybe there is a build setting that I need to enable that would do this, but I could not find anything.

We're having the same issue. Builds were working fine yesterday, now they're stuck right at the end of build phase in xcodecloud as it's being sent to App Store Connect.

I think we're having the same problem. Xcode Cloud build was stuck on Prepare Build for App Store Connect for 13 hours. App Store Connect was showing the build as Processing. This morning I cancelled the build. Xcode Cloud status is Cancelled, but App Store Connect still showing as Processing. Started a new build. Same issue. So now we have two builds stuck on Processing. I contacted support with details. Case ID is 102802250079

If I’m reading FB21249476 correctly, there should be improvements in this space in Xcode 26.3b2 (25D5101c) [1]. I recommend that you re-test with that build. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] This only just started seeding, so Feedback Assistant hasn’t had time to notify you about it.

Having the same issue here, our builds are stuck on processing for over 8 hours now

Also got 2 iOS builds stuck in processing for about 6+ hours now

Notarisation is a read-only process, so notarising an app can’t cause it to stop working. Usually problems like this are caused by the hardened runtime. Notarisation requires that you enable the hardened runtime, so folks re-sign their app with that enabled and then it fails. There are two ways you can approach that: Run the Developer ID-signed build before you notarise it. This should hang in the same way. Enable the hardened runtime on your day-to-day development builds. This lets you debug this issue like you would any other hang. Resolving Trusted Execution Problems has a section on debugging hardened runtime issues, namely Resolving Hardened Runtime Incompatibilities. Oh, one more thing. This is problematic: codesign --force --deep --verify --verbose --option runtime --sign Developer ID Application: ORG NAME (ZZZZZZZZZ) path/to/app.app To start, you’re supplying both --verify and --sign, which is never a good idea. For any given invocation of codesign, you should do one or the other. Ne

[quote='812598021, yccheok, /thread/812598, /profile/yccheok'] Is nonisolated still an appropriate way to ensure code runs on a background thread? [/quote] Yes and no. There are a couple of Swift Evolution proposals that describe this change in detail: SE-0461 Run nonisolated async functions on the caller's actor by default SE-0466 Control default actor isolation inference And, as you’ve noticed, there are Xcode build settings that affect this stuff. So, you have a couple of options: You can tweak your build settings and leave your code as is. Or you can move forward to the new build settings and tweak your code. I generally favour the second option, but I can understand folks preferring the first option, especially when wrangling a large project. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

The Apple Developer Forums are primary focused on helping developers build apps and other products for Apple’s various platforms. Given that, I have two suggestions for you: File a bug using Feedback Assistant. Seek help in the Apple Support Community, run by Apple Support. Or both (-: Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com