We also see this issue, interestingly when Xcode cloud shows the call to run the generated script, the surrounding sandbox-exec does seem to say that writing to this directory should be allowed, yet it still fails: Swift/ErrorType.swift:200: Fatal error: Error raised at top level: Error Domain=NSCocoaErrorDomain Code=513 "You don’t have permission to save the file “String+TransactionsAccessors.swift” in the folder “StringsGeneratorPlugin”." UserInfo={NSURL=file:///Volumes/workspace/DerivedData/SourcePackages/plugins/SampleApp.output/SampleApp/StringsGeneratorPlugin/String+TransactionsAccessors.swift, NSUserStringVariant=Folder, NSUnderlyingError=0x600003104330 {Error Domain=NSPOSIXErrorDomain Code=1 "Operation not permitted"}} then in the call to sandbox-exec /Volumes/workspace/DerivedData/Build/Intermediates.noindex/SampleApp.build/Debug-iphonesimulator/SampleApp.build/Script-7981050304838536995.sh: line 17: 12085 Illegal instruction: 4 /usr/bin/sandbox-exec -p "(version 1) (deny default) (import \"system.sb\") (allow file-read*) (allow process*) (allow file-write* (subpath \"/private/tmp\") (subpath \"/private/var/folders/22/cm0mxjnn4zg5l2rs2l3b51qr0000gn/T\") ) (deny file-write* (subpath \"/Volumes/workspace/repository/SampleApp\") ) (allow file-write* (subpath \"/Volumes/workspace/DerivedData/SourcePackages/plugins/SampleApp.output/SampleApp/StringsGeneratorPlugin\") )

Ah nvm, a fresh build resolved it - What a thrill though!

Seeing this as well, not all builds fail but the majority did for a period - also we had accidentally started running builds on MacOS Tahoe. Swapping back to Sequoia but unsure if that's actually the root cause here. Duped DaeLee's feedback (20269471) with this new feedback FB20270682

Seeing this as well. When I look at the crash log for the Simulator I see an issue where it seems to be crashing in unrelated apps. Worth raising a feedback here as well and uploading the ips files (+ the sysdiagnose). I'll do the same later today and share the number here.

Seeing this as well. I don't see those exact errors in the log. In our case it repeatedly mentions: 2025-12-14T23:42:24.246116551Z error: exportArchive There is a problem with the request entity 2025-12-14T23:42:24.246119266Z 2025-12-14T23:42:24.246121303Z error: exportArchive No signing certificate "iOS Development" found 2025-12-14T23:42:24.246124727Z 2025-12-14T23:42:24.246126906Z error: exportArchive There is a problem with the request entity 2025-12-14T23:42:24.246129486Z 2025-12-14T23:42:24.246131437Z error: exportArchive No signing certificate "iOS Development" found Which is odd as we use cloud managed signing. I do see a Development certificate created by Xcode cloud. The app id that references is setup for iOS. I don't see an Xcode cloud generated Provisioning profile in the development portal, but I can't recall if they show up there. FB21343022

I'm seeing a similar issue with just Xcode cloud builds. Feedback here: FB21343022 For us, changing Xcode version on Xcode cloud doesn't resolve. To repeat details from the feedback for those at home: We see the following error on repeated Xcode cloud builds when trying to archive for “iOS App Store”. Export archive for development distribution Command exited with non-zero exit-code: 70 The “Archive Build” step is failing with what looks like some internal error. Xcode Version: 26.1.1 (17B100) macOS Version : macOS Tahoe 26.1 (25B78) Attached are the logs, within the relevant part I see this repeated (truncated here for reference and brevity) 2025-12-14T23:42:24.246116551Z error: exportArchive There is a problem with the request entity 2025-12-14T23:42:24.246119266Z 2025-12-14T23:42:24.246121303Z error: exportArchive No signing certificate "iOS Development" found 2025-12-14T23:42:24.246124727Z 2025-12-14T23:42:24.246126906Z error: exportArchive There is a problem with the request entity 2025-12-14T23:42:24.246129486Z 2025-12-14T23:42:24.246131437Z error: exportArchive No signing certificate "iOS Development" found

I had a similar issue recently and I had to revoke the Xcode managed certs from the portal. Then it came right. I'm not sure why this happened! I think there's a limit on the number of certs you can have and something got borked?

I imagine given Tahoe was the last release to support x86, that we'll get arm Xcode Cloud this year.