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.

The build status has a green check in Xcode Cloud, but TestFlight see no builds and suggest that I submit one. Then it provides a link to an incredibly unhelpful list of upload tools, at least one of which suggests creating a developer account!!!

All our builds getting stuck on the que. https://developer.apple.com/system-status/ is not showing xcode cloud as down.

Issue Description I'm have Local Swift Package which contains binary target to private github releases url is formed like below: https://api.github.com/repo/{owner}/{repo}/releases/assets/{asset_id}.zip I register the private repo to the xcodecloud, but still xcodecloud does not recognize "api.github.com" domain. So build keeps fails at downloading binary artifact. https://github.com/{owner}/{repo}/releases/download/{tag}/Myframework.xcframework.zip is not a valid choice since this kind of url, is not supported for private repository. Proposed Solution Please add authorization to the "api.github.com" like normal "github.com".

I am experiencing significant delays with TestFlight Internal Testing processing in Xcode Cloud. The build has been stuck in the processing state for over 8 hours, which is significantly longer than our usual deployment time. Issue Details: Product: Xcode Cloud / TestFlight Internal Testing Time in Processing: 8+ hours Build Status: Stuck in "Processing for TestFlight Internal Testing" Workflow Type: iOS App Distribution Steps to Reproduce: Triggered Xcode Cloud workflow for iOS app Build completed successfully TestFlight Internal Testing processing started Processing has not completed after 8+ hours Technical Information: Xcode Version: Xcode 15.4 iOS App Target Version: iOS16.4 Attempted Troubleshooting: Verified all certificates and provisioning profiles are valid and up-to-date Confirmed the build was successful in Xcode Cloud Checked that the app binary size has not changed significantly Reviewed all workflow logs for potential errors or warnings Is there a known issue with TestFlight processing times currently? Are there any steps we can take to resolve or expedite this process? Can you investigate if there are any specific issues with our build that might be causing this delay? Please let me know if you need any additional information to assist with this issue. App Information: App Name:Simple Voice Recorder - Audio Bundle Identifier: id6443528409 Thank you for your assistance in resolving this issue. Best regards,

My Xcode cloud pipeline seems to be stuck at 46% inside the archiving step for some reason. When I run my project locally, it works, and uploading my build manually through Xcode to app store connect works too. However, when I try to build my app using Xcode cloud, it gets stuck after the archiving step has successfully completed. All checkmarks are green, but the archiving step does not terminate after one hour. I tried switching the cloud Xcode version, the cloud macOS version, changing my code. Nothing works and Xcode cloud is completely bricked. How do I fix this? There is no error message at all. The build is just stuck at 46% and nothing happens.

I use xcode to rename a view in my project. It renamed the file, the struct, and all related items. However; since doing that my xcode cloud workflow fails, indicating that the it cannot find it in scope. I have confirmed that the file shows up in my BuildPhases - Compile Sources. I have confirmed it exists in my git repo, but Xcode Cloud still fails to find it in scope. I have confirmed it shows up in the correct Target Membership. I even tried removing it from the BuildPhases and re-adding it. How can I resolve this issue? Is there something else I can look at? btw, application builds fine locally on my machine.

My organization just started having problems with Xcode Cloud this week. We have created a pretty simple 'Build on Pull Request'. The problem is our builds have started failing immediately because with the error. "Could not resolve package dependencies:" What is even more frustrating is the dependency that reported failed seem to changes every time. This did not happen before this week. Our build process is fairly vanilla, through Xcode. (We are NOT using CLI xcodebuild) I can build a locally just fine from a clean build, and cleaning derived data. Nothing has changed in our dependencies. We are not using any private dependencies. So I am stumped on what else to do how to debug, and fix this, because I am not sure how to encourage the Xcode Cloud build runner/server that the dependences are available and to jsut go get them. Any help would be great, because we just started using Xcode Cloud to get away from Fastlane (which was causing problems), and it would be frustrating if this is a sign of things to come. Sincerely, Stan

I'm working on Apple Watch UI tests and have noticed different results between local and Xcode Cloud environments. I tested all cases locally, and they worked fine. However, when running the tests on Xcode Cloud, some issues caused them to fail: The test requires clicking a button to display the built-in keyboard, but on Xcode Cloud, the keyboard never appears, no matter how long I wait. The app unexpectedly closes during testing, displaying the error message: "Failed to launch application {Your app} is not running." These failures occurred on two different simulator destinations (Ultra 49mm 11.2 / Series 7 45mm 11.2) and can only be reproduced on specific simulators. Has anyone encountered a similar issue?

when Intergrate WeChat OpenSdk , Xcode Cloud cannot build success, beacause Xcode Cloud cannot resolve dldir1.qq.com

There seems to be a problem to a specific Apple Developer Account regarding Xcode Cloud Distribution (Signing). The Xcode Cloud Error Invalid Signature. Code failed to satisfy specified code requirement(s). The file at path “XcodeCloudTest.app/XcodeCloudTest” 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. Investigation Apple Developer Forums This issue seems to be known: https://developer.apple.com/forums/thread/746210 Debugging by ourselves We setup an example Xcode project from a default iOS Xcode app template to rule out any project issues. This example project failed with the same error as stated above. In the next step we tried the same example project with a different Apple Developer Account and it successfully distributed the example App through Xcode Cloud. Conclusion It seems like there is no setup issue on developer-side, because our example project works out-of-the-box on a different Apple Developer Account. Our only hope is that Apple will have a look on our Developer Account. Maybe there is some internal setting.

Hi, I'm trying to use the change url functionality to switch my Xcode Cloud setup from Gitlab.com to my self hosted Gitlab instance. The setup process completes successfully, however, Xcode Cloud does not create any web hooks in my repo and also is not able to fetch any branch/tag information from the Gitlab instance. There is also no error displayed on Xcode Cloud UI. I even tried to debug by looking at requests on my server to see if there are any clues, to no avail. The only clue seems to be that in my repositories page, I see the instance listed but the row is highlighted red (which I assume means there's an issue with the connection). The last accessed date is also empty. The call to the /repos-v3 endpoint from App Store Connect seems to indicate there's an authentication issue: { "primary_repos" : [ { "repo" : { "id" : "xxxxxxxxxxx", "http_clone_url" : "xxxxxxxxxxx", "owner_name" : "xxxxxxxxxxx", "repo_name" : "xxxxxxxxxxx-ios", "repo_id" : "7", "provider" : "gitlab-hosted", "ssh_clone_url" : "ssh://xxxxxxxxxxx", "scp_clone_url" : "git@xxxxxxxxxxx", "default_branch" : "master" }, "authorization_state" : "unauthorized" } ], "additional_repos" : [ ], "unauthorized_repos" : [ ], "revoked_repos" : [ ] } On my end, when I try to add the repository to Xcode Cloud, I see a few requests to my GitLab instance, all of which succeed with 200: {"time":"2025-03-11T21:10:26.217Z","severity":"INFO","duration_s":0.05674,"db_duration_s":0.00567,"view_duration_s":0.05107,"status":200,"method":"GET","path":"/api/v4/user",.... {"time":"2025-03-11T21:10:26.797Z","severity":"INFO","duration_s":0.16682,"db_duration_s":0.02024,"view_duration_s":0.14658,"status":200,"method":"GET","path":"/api/v4/projects/xxxxxx%2Fxxxxxx-ios",.... {"time":"2025-03-11T21:10:28.298Z","severity":"INFO","duration_s":0.06617,"db_duration_s":0.00835,"view_duration_s":0.05782,"status":200,"method":"GET","path":"/api/v4/user",.... {"time":"2025-03-11T21:10:28.867Z","severity":"INFO","duration_s":0.21071,"db_duration_s":0.03075,"view_duration_s":0.17996,"status":200,"method":"GET","path":"/api/v4/projects/xxxxxx%2Fxxxxxx-ios",.... {"time":"2025-03-11T21:10:30.621Z","severity":"INFO","duration_s":0.15613,"db_duration_s":0.01842,"view_duration_s":0.13771,"status":200,"method":"GET","path":"/api/v4/projects/7",.... {"time":"2025-03-11T21:10:31.239Z","severity":"INFO","duration_s":0.1672,"db_duration_s":0.01828,"view_duration_s":0.14892,"status":200,"method":"GET","path":"/api/v4/projects/7",..... At this point I'm sure this is some sort of a bug with Xcode Cloud since the requests do succeed but Xcode Cloud is unable to process the responses and identify the correct branches and tags, as well as set the web hook for the repo.

Hey everyone, We’re running into a frustrating issue with Xcode Cloud builds submitted to App Store Review. After every build, we must manually delete all code signing certificates generated by Xcode Cloud; otherwise, the reviewers can’t open the exported App Store app. When they try to open it, they see the error: “Apple Information Security: A process was blocked from running and moved to Trash: [Our App Name]” Oddly enough, if we delete all Xcode Cloud-generated certificates and then trigger a new Xcode Cloud build, the problem temporarily disappears—until the next submission, where we have to repeat the process. Has anyone else encountered this issue? Any recommendations on how to prevent this from happening? We’d rather not keep trashing certificates after every build. Thanks!

Hello! I'm trying to build my flutter app through xcode cloud, but im getting following error: Command exited with non-zero exit-code: 65 Run command: 'xcodebuild archive -workspace /Volumes/workspace/repository/ios/Runner.xcworkspace -scheme Runner -destination generic/platform=iOS -archivePath /Volumes/workspace/build.xcarchive -derivedDataPath /Volumes/workspace/DerivedData -resultBundleVersion 3 -resultBundlePath /Volumes/workspace/resultbundle.xcresult -resultStreamPath /Volumes/workspace/tmp/resultBundleStream97053cd8-9db9-41c6-9dc8-a9fc142bacb6.json -IDEPostProgressNotifications=YES CODE_SIGN_IDENTITY=- AD_HOC_CODE_SIGNING_ALLOWED=YES CODE_SIGN_STYLE=Automatic DEVELOPMENT_TEAM={development_team_here} COMPILER_INDEX_STORE_ENABLE=NO -hideShellScriptEnvironment' When i build locally, it works fine, tried both debug/release modes, but in the cloud archive fails. Also have following message in xcode cloud: `'Flutter/Flutter.h' file not found GeneratedPluginRegistrant.h:10` failed to emit precompiled header '/Volumes/workspace/DerivedData/Build/Intermediates.noindex/ArchiveIntermediates/Runner/PrecompiledHeaders/Runner-Bridging-Header-swift_2QGFV1FVTQX2Z-clang_IX5TH88559CY.pch' for bridging header '/Volumes/workspace/repository/ios/Runner/Runner-Bridging-Header.h'

We are trying to access the Sonar and Nexus remote servers from Xcode Cloud, to see the coverage percentage and artifact upload but we are unable to do so as it says "host not resolved." Could you please help us with accessing Nexus, Sonar, Dynatrace, and other tools from Xcode Cloud? We connected to network team of organization to enable firewall but they need the Xcode cloud server ip details Regards, Bala

This appears to be the same issue as wasresolved here, but given that post is marked as solved, I thought it appropriate to open a new thread. I have no access to build artefacts for any of the App Store Connect teams I'm a member of. I have Admin or App Manager permissions for the teams I've tried. Clicking the download link for any artefact directs to a single json string: {"message":"You are not authorized to access this team’s resources."} Trying through the build navigator in Xcode 16.3 crashes Xcode.

Hello. We've built our app with Xcode cloud until now. And we faced a issue after we changed some dependencies in SPM. the problems occur while resolving below dependencies https://github.com/naver/naveridlogin-sdk-ios-swift https://github.com/navermaps/SPM-NMapsMap with below message. xcodebuild: error: Could not resolve package dependencies: failed downloading 'https://repository.map.naver.com/archive/pod/NMapsMap/3.21.0/NMapsMap.zip' which is required by binary target 'NMapsMapBinary': downloadError("A server with the specified hostname could not be found.") failed downloading 'https://repository.map.naver.com/archive/pod/NMapsGeometry/1.0.2/NMapsGeometry.zip' which is required by binary target 'NMapsGeometry': downloadError("A server with the specified hostname could not be found.") is there a way to handle this error by ourselves? we need your help. thank you.

I am taking this error. I tried everything , changing repository, manually edit checksum but it seems that its not working. [!] Error installing boost Verification checksum was incorrect, expected f0397ba6e982c4450f27bf32a2a83292aba035b827a5623a14636ea583318c41, got 79e6d3f986444e5a80afbeccdaf2d1c1cf964baa8d766d20859d653a16c39848 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.

I have an XCode Cloud CI/CD process that's been in place for over a year now, hooked up to the project's GitLab repository. Yesterday it lost connection to the repo, and I can't get it to reconnect. Here's the error I see when I click on the "reconnect" button: The repo still exists, obviously, and I still have maintainer access. I did notice that my private key that I use to connect XCode to GitLab had expired, so I created a new one, but that didn't resolve the issue. Another thing I noticed is that when I try to look at my builds in the console, it tells me to link my gitlab account with my Apple account: But when I click the Link Accounts button, nothing happens. Is there a different way to link the accounts? Is it possible that's what the issue is?