As mentioned in the linked post, I can archive the project locally but not via Xcode Cloud. I have also created a new project, but the same thing happens here.
https://developer.apple.com/forums/thread/746210
Error Code:
ITMS-90035: Invalid Signature. Code failed to satisfy specified code requirement(s). The file at path “{AppName}.app/{AppName}” 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.
Xcode Cloud
RSS for tagAutomate workflows to test, analyze, build, and distribute your app, and integrate them with other developer tools, such as TestFlight and App Store Connect.
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Created
Since Dec 18th, my Xcode Cloud builds (for multiple apps) have been failing with this error:
Command line name "app-store" is deprecated. Use "app-store-connect" instead.
I haven't made any changes to my system, signing, etc, and two separate apps started failing at the same time. No matter what I change on my Workflows (environment, new workflow from scratch, etc), nothing seems to fix it, which leads me to believe this is a bug with Xcode Cloud itself.
I've logged FB21456291 already, but just wanted to post here to see if I'm missing something.
Hello guys, recently I integrated a third-party library into my code to handle blur effects (Glur). This library leverages Metal's compute capabilities and appears to automatically depend on the Metal toolchain during the build process. When using Xcode Cloud, the archive step consistently fails with a "CompileMetalFile Failed" error. However, when I manually archive the project in Xcode locally, everything works fine without any issues. I’ve confirmed that the macOS and Xcode versions specified in my Xcode Cloud workflow are correct. Reply if you know how to fix it or it will be fixed future, thanks.
I'm using Xcode 26.2(17C52) and macOS(15.7.1 (24G231))
I’m trying to integrate our app with the iXGuard obfuscation tool, which needs to run in the archive post-actions step in Xcode Cloud. The issue is: iXGuard takes a long time to complete and, during its execution, does not generate any console output or logs in the Archive Post-actions step.
Problem:
When Archive Post-actions runs for a long time without producing log output, Xcode Cloud triggers a timeout and the workflow stops before running the next CI step (e.g., ci_post_xcodebuild.sh). Even though the script continues running in the background, the workflow is aborted due to inactivity in the logs.
Workaround Tried:
As a workaround, I have ci_post_xcodebuild.sh print the logs generated by archive post-actions. However, this does not help in my case since the timeout occurs before ci_post_xcodebuild.sh even runs.
Error:
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.
Question:
Is there a recommended way to prevent Xcode Cloud from timing out during long-running steps that do not produce log output?
Are there best practices for keeping the workflow alive with periodic logs during Archive Post-actions?
Any support or workaround for integrating tools like iXGuard that require significant processing time after the archive step?
Thanks in advance for your help!
Just learnt today that personal development teams do not support the Push Notifications and iCloud capabilities, is there any workaround besides pay another 99 for an enterprise development account? Thanks in advance.
Topic:
Developer Tools & Services
SubTopic:
Xcode Cloud
After pushing to a branch which is automatically configured to build and distribute on TestFlight, I found no way to log on and check Xcode cloud builds and nothing being pushed to that branch was building or showing up elsewhere in App Store Connect.