When building xcode project of an application with login item included/embedded (another target), locally it works without problems. But when building on xcode cloud, we are getting the error: ITMS-90286: Invalid code signing entitlements - Your application bundle’s signature contains code signing entitlements that aren’t supported on macOS. Specifically, the “***.***.***” value for the com.apple.application-identifier key in “Path_to_login_Item” isn’t supported. This value should be a string that starts with your Team ID, followed by a dot (“.”), followed by the bundle ID. If there are no capabilities added to the login item's target (only com.apple.security.inherit and App Sandbox), the project builds without errors. But our login item needs to access a database in app group container and sync its data with iCloud, so after adding iCloud and App Group entitlements, building on xcode cloud fails with the error written above. Locally it builds and runs without problems. So, what should be done to fix this issue when building on xcode cloud?

I have checked that my scheme is shared and I do in fact have the scheme in my xcode project. But whenever I try to run Xcode cloud, it fails with the message that "A scheme named 'MyAppScheme' does not exist in MyAppProject.xcodeproj" Any tips on what I could be doing wrong?

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.

Hello guys, I currently have a problem with Xcode cloud. When I setup a simple workflow in my Xcode project that just archives it and builds the project for TestFlight Internal testing, it will fail and give the following error: Invalid Signature. Code failed to satisfy specified code requirement(s). The file at path “DropIn.app/DropIn” 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. I've already been searching for solutions and double checked the documentation. My Xcode project is a simple iOS app with the app target and two other targets for tests and UI tests. I made sure the checkbox "Automatically manage signing" is ticked in all targets. The workflow has only one action "Archive - iOS" with TestFlight (Internal Testing Only) and a post-action "TestFlight Internal Testing - iOS" with an internal testing group assigned. I've seen people having similar problems where it turned out they had a non roman character in their name? This would also affect me if that's the case, since my name includes "ö". I also checked on app store connect and already deleted xcode cloud data, removed all certificates recreated the workflow, but it still gives this error. Any ideas on how to fix this?

My Xcode Cloud workflows tell me the 'Latest Release' Xcode that it's using is Xcode 16.1 Release Candidate (16B40) Obviously that is well out of date at this point, plus, an RC is not a release version. How can I tell Xcode Cloud to always use the latest (non-RC) release version?

I've recently added iCloud backup on my chat app. Conversations are backing up fine but some users are losing their chats and when I see the telemetry it show "BAD_REQUEST" error. I couldn't find any details or solution for it. Does anyone has any idea what it could be? My development scheme is already fully deployed to production.

Hi folks, I've been having this issue for the last few months, where Xcode Cloud fails to resolve Swift package dependencies while compiling my builds, seemingly at random. Some of my Xcode Cloud builds will fail after several minutes, with an error log looking like that : xcodebuild: error: Could not resolve package dependencies: failed downloading 'https://dl.google.com/firebase/ios/bin/grpc/1.62.2/rc0/grpcpp.zip' which is required by binary target 'grpcpp': downloadError("The request timed out.") Whenever this happens, I have to manually restart an Xcode Cloud build process (or several builds, since the error can happen multiple times in a row), to the point it's becoming increasingly painful to rely on Xcode Cloud for my workflow. The failing packages are mostly random (meaning, it's not always the same one that Xcode fails to resolve), but they are always publicly accessible, even though I have an environment variable set in my Xcode workflows to retrieve a single Github private dependency (maybe this has some kind of importance). Could anyone tell me if this is an isolated issue, or if I could do anything on my end to resolve this ? Thank you !

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.***.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!

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?

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.

Possible a duplicate of this resolved post from November, but I can't access any Xcode Cloud artefacts with the message "You are not authorized to access this team’s resources." Trying to access from within Xcode itself crashes Xcode 🙃

Since today, all our team members cannot download artifacts from Xcode Cloud builds. We get a JSON response that contains: {"message":"You are not authorized to access this team’s resources."} System Status doesn't show any issues at the time. Is there an action we can follow to restore proper access? Thank you in advance.

Recently, I’ve noticed that the Archive workflow on Xcode Cloud frequently fails randomly with the following error: ❌ Exporting for App Store Distribution failed. Please download the logs artifact for more information I’m not sure if this issue is on my side or if it’s related to Xcode Cloud itself. Has anyone encountered a similar problem?

Hi, Our organisation just ran out of the included Xcode Cloud hours. I now want to upgrade (I am the account holder). There does not seem to be a way to do this on the Apple Developer and/or App Store Connect websites, as you'd expect. The Get started with Xcode Cloud page mentions that I need to use the Apple Developer app. However, when I sign up to this in the Apple Developer app, the account shown when pressing Subscribe is my personal account, not any account related to the organization: It is impossible to change the payment details. How can I use the organization account to pay for this, as I obviously do not want to get charged to my personal account? Thanks.

This started on April 4. System status says it's fixed, but I'm still having issues

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

Hello, I uploaded a new build to TestFlight, and it has been about an hour since the processing was completed. However, the update is still not showing up in the TestFlight app. From my experience, the update usually appears within 10 to 30 minutes, but this time it is taking unusually long. I’m wondering if anyone else has experienced a similar issue and found a solution. Any advice or guidance would be greatly appreciated. Thank you!

Log shows: Run command: 'xcodebuild -exportArchive -archivePath /Volumes/workspace/tmp/d3c9c43f-e24e-4ad9-882d-d0179ab3149b.xcarchive -exportPath /Volumes/workspace/developmentexport -exportOptionsPlist /Volumes/workspace/ci/development-exportoptions.plist '-DVTPortalRequest.Endpoint=http://172.16.182.66:8089' -DVTProvisioningIsManaged=YES -IDEDistributionLogDirectory=/Volumes/workspace/tmp/development-export-archive-logs -DVTSkipCertificateValidityCheck=YES -DVTServicesLogLevel=3' Command exited with non-zero exit-code: 70

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'