It is a bit strange what Xcode Cloud has implemented on how they manage the Build Numbers https://developer.apple.com/documentation/xcode/setting-the-next-build-number-for-xcode-cloud-builds Intead of just looking at the project configuration as the source of truth, they run their own build number and totally ignore the project config value. Also, interesting that instead of solving it they have a "Set Build Number" menu in the settings which is a pain to manually manage everytime they got out of sync. Is there any way to turn this madness off and consider the project config as the source of truth?

Hi Team, Please help me to resolve these issues as i am unable to run xcode ci cd due to code signing issue.

Hi - I was recently added to Apple Developer Team, and I am trying to upload an App to our Team's App Store Connect account for TestFlight distribution. I am trying to use XCode Cloud to this all automatically, but it is currently giving me this error: "Invalid Bundle ID. Bundle ID "com.XXX.YYY" could not be automatically registered because it is not available. Update the bundle ID of your project and try again." I am not sure if this is related to the fact that when I try to associate my XCode Account (XCode -> Settings -> Accounts), I only see my (Personal Team) account even after removing that account and re-adding it. Additionally, when I go my App -> Targets -> Signing & Capabilities and I check / uncheck automatically manage signing. I only see my Personal Team account. When I try to download a Provisioning Profile, I see "No Valid Teams, Unable to Find Any Valid Teams." I need to keep the bundle ID of the project as is because it is associated with a Firebase backend. What should I try next? Thanks!

I've noticed that when using the Test action in an Xcode Cloud workflow, the xcodebuild command includes COMPILER_INDEX_STORE_ENABLE=NO while performing build-for-testing. This disables the index store, which is required by tools like Periphery to analyze unused code. Without indexing, Periphery triggers a fresh build internally, resulting in a significant increase in CI build time. Is there any way to enable indexing (COMPILER_INDEX_STORE_ENABLE=YES) on Xcode Cloud? Or alternatively, is there a recommended workaround to generate and access the index store? Any help is appreciated.

Can anyone help me resolve this lookup issue? This has been breaking builds for months. We make no changes and after a couple hours it works. It seems like Apple resolvers are getting a failure and then negatively caching the failure. Immediate subsequent runs extend the failure duration this is one of our installs from a pod install installing onnxruntime-c (1.21.0) [!] Error installing onnxruntime-c [!] /usr/bin/curl -f -L -o /Volumes/workspace/tmp/d20250730-29606-1v7ovh/file.zip https://download.onnxruntime.ai/pod-archive-onnxruntime-c-1.21.0.zip --create-dirs --netrc-optional --retry 2 -A 'CocoaPods/1.16.2 cocoapods-downloader/2.1' % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0curl: (6) Could not resolve host: download.onnxruntime.ai

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 have Admin role but whenever I select the tab "Xcode Cloud" on any app, the page is not loaded. I am developer from Russia, its banned for russian users??? Please help, i cant update app

I have a workflow where I want to specifically run some tests in the iOS 18 simulator. All while using Xcode 26 on Xcode Cloud. In my Xcode Cloud workflow I can set the iOS version, but just iOS 16, 17 and 26, but no 18? I'm very confused here Not sure which is the right channel anyway to request support to Xcode Cloud too

Hello, my builds keep failing in Xcode Cloud at the creation of the archive for tesflight. I am receiving an email mentioning "ITMS-90035: Invalid Signature" TMS-90035: Invalid Signature - Code failed to satisfy specified code requirement(s). The file at path “BASELog.app/BASELog” 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 thing is the archives which are not intended for testflight not App Store connect are not failing. I think I have the required distribution certificates (initially they were created by API for Xcode Icloud, I add 3, revoked them and recreated one manually and the other from Xcode directly) : even though certificats seems ok, in Xcode I see a dev certificate in the managed release and if I try to force a distribution certificate in the build I then get the following warning It looks like my managed profile is not behaving properly, like not embedding a distribution certificate. I looked on the web for the signing issues, and I have found in other threads an issue with assets having special charsets. I checked on my side, the only thing I see is my app icon is named "icon_v1.png" I assume it shouldn't be an issue. I dont see any special char anywhere else in the sources name. Anyone has any idea on what is causing those build fails on the archive?

We have a repository that contains two components: The SDK codebase A sample app that uses the SDK for testing purposes We’ve set up an Xcode Cloud pipeline for the sample app. In this setup, the sample app references the SDK from a local path. Within the ci_post_clone script, we build the SDK project for both the simulator and device, create an .xcframework, and then build the sample app. Everything works fine — the sample app builds successfully, and the resulting archive is uploaded to Xcode Cloud as an artifact. However, I also want to share the generated .xcframework with customers by including it as an artifact in the pipeline. The issue is that the .xcframework doesn’t appear in the App Store Connect build artifacts. I’ve tried the following without success: Placing the .xcframework inside a folder named artifacts at both the repository root and the project root Copying the .xcframework to the $CI_ARCHIVE_PATH directory There isn’t much documentation available on custom artifact creation in Xcode Cloud. Can someone point me to proper documentation or confirm if this is supported? I assume it should be possible, as this is a common workflow for SDK pipelines.

【溦N51888M】腾龙公司直属会员怎么开户【罔纸 211239.com 】输入官惘到浏览器打开联系24小时在线业务人员办理上下，打开公司官网. 二、点击主页右上角注册按钮. 三、填写账号信息. 四、输入手机号，验证码，密码. 五、勾选用户协议，完成注册协议，完成注册. 注意：若出现账号已存在」提示，需重新设置唯一账号名称

I am curious whether Xcode Cloud uses npm internally when you run it. With the recent and still simmering Shai-Hulud 2.0 worm, we are just a little concerned. As such, any information would be appreciated. Thank you in advance!

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.

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!

Good morning all, We have an on-premise instance of Bitbucket (v8.19.25), using a custom port. We'd like to try using Xcode Cloud, compare to our current CI/CD provider. Once I have to select my source control provider to grant access, I select Bitbucket Server. If I try to input the Host Name with, or without a port, I'm receiving this response: { "message": "An error occurred", "details": [ { "message": "An error occurred", "source": "host" } ], "actions": [], "recovery_actions": [ { "dismiss_label": "OK" }, { "feedback_label": "Provide Feedback", "feedback_component": "Xcode Cloud | New Bugs" } ], "should_show_error": true } Which, of course, doesn't help me in the slightest to understand why the connection fails. I do notice that the request to https://appstoreconnect.apple.com/ci/api/teams/<id>/setup-flow/scm-repositories in the web inspector already includes a host and port that I use to clone the repository locally. However, the web-based interface of Bitbucket doesn't include that port. So, if I clone a repo: ssh://<bitbucket-instance>:<port>, but if I look at pull requests: https://`. My colleagues have already determined that there shouldn't be any firewall rules or gateway limits, so Bitbucket should be reachable. No VPN either. How can I continue to fix this?

My workflow is using Xcode 16.4 and macOS Tahoe 26.2 (25C56). I am trying to change Xcode version to 26.2. When I click Save after some time I get "Something went wrong" error message without any additional details (see screenshot). I get the same error for the following cases: Tried changing a different workflow Tried to deactivate a workflow Tried various combinations of Xcode (26.1, 26.1.1, 26.2) + mac OS (26.1, 26.2) Tried creating a new workflow with Xcode 26.2 (haven't tried any other Xcode versions though)

Hi, our Xcode Cloud runs produce dsyms for test targets that massively increase the artifacts size, more specifically the "Test Products for" zip, that slows down the build due to the "upload artifacts" phase. These dsyms are useless, so we would like to stop producing them on Xcode Cloud builds. Consider that the workflow uses the autogenerated scheme for a package that's part of the Xcode project. How can we tell Xcode Cloud to not produce dsyms?

I'm attempting to use Cloud Signing to export the Release version of 3 different apps for App Store, as described in https://developer.apple.com/videos/play/wwdc2021/10204/ The process completes successfully, and appears to be signed correctly, with a newly-created certificate in the developer portal of type "Distribution Managed". When I upload to App Store Connect however, I see the following error for several third-party Swift packages, distributed as frameworks: Validation failed (409) Invalid Signature. Code failed to satisfy specified code requirement(s). The file at path “MyApp.app/Frameworks/MyFramework.framework/MyFramework” 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. If I have a manually created Distribution certificate installed in the keychain at the point of export, the same archive is signed with that certificate, and is accepted by App Store Connect without issue. The xcodebuild command I am using (roughly): xcodebuild -exportArchive \ -archivePath "$ARCHIVE_PATH" \ -exportPath "$EXPORT_PATH" \ -exportOptionsPlist "$EXPORT_OPTIONS" \ -authenticationKeyPath "$API_KEY" \ -authenticationKeyID "$API_KEY_ID" \ -authenticationKeyIssuerID "$API_KEY_ISSUER" \ -allowProvisioningUpdates The plist: <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "<http://www.apple.com/DTDs/PropertyList-1.0.dtd>"> <plist version="1.0"> <dict> <key>method</key> <string>app-store-connect</string> <key>teamID</key> <string>$TEAM</string> <key>uploadSymbols</key> <true/> <key>signingStyle</key> <string>automatic</string> </dict> </plist> Is what I’m trying to do supported? Is this a bug?

I have an app that downloads different pods, but they suddenly stopped: curl: (6) Could not resolve host: dl.google.com Warning: Problem : timeout. Will retry in 1 seconds. curl: (6) Could not resolve host: dl.google.com Warning: Problem : timeout. Will retry in 2 seconds. 1 retries left. curl: (6) Could not resolve host: dl.google.com Earlier it did not find https://cdn.cocoapods.org Temp issue or do you have to setup DNS of some sort?

This happens way too often (see the image below). Especially today. I used this snippet from the offical Rust website to install rustup: curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh -s -- -y Run ci_post_clone.sh script Run command: 'cd /Volumes/workspace/repository/apps/app/ios/ci_scripts && /Volumes/workspace/repository/apps/app/ios/ci_scripts/ci_post_clone.sh' info: downloading installer warn: curl: (6) Could not resolve host: static.rust-lang.org curl: (6) Could not resolve host: static.rust-lang.org curl: (6) Could not resolve host: static.rust-lang.org curl: (6) Could not resolve host: static.rust-lang.org error: command failed: downloader https://static.rust-lang.org/rustup/dist/x86_64-apple-darwin/rustup-init /var/folders/6h/_32gb9js77g6c54h3q7g6q1h0000gn/T/tmp.yave38jqWa/rustup-init x86_64-apple-darwin Error: Command exited with non-zero exit-code: 1 Warning: Running ci_post_clone.sh script failed (exited with code 1). Executable scripts are run using the interpreter specified in the shebang line.