My app is approved for the Web Browser Public Key Credential Request managed capability and has it added to its App ID Configuration: It has been added to my entitlements file: I am able to build and run unit tests in Xcode locally using my managed profile. When I push changes and Xcode Cloud tries to build and run the app, I get the following error: Mirrai encountered an error (Failed to install or launch the test runner. (Underlying Error: Could not launch “MirraiTests”. Runningboard has returned error 5. Please check the system logs for the underlying cause of the error. (Underlying Error: The operation couldn’t be completed. Launch failed. (Underlying Error: Launchd job spawn failed)))) Removing just the com.apple.developer.web-browser.public-key-credential entitlement, with no other changes, results in all tests passing on Xcode Cloud. Some thoughts: In project settings, the test target has a different bundle id (appending Tests to the app bundle id). Under "Certificates, Identifiers & Profiles," the managed capability is added to the bundle id but it is an explicit bundle id and not a wildcard. Do I need to apply for the managed capability for the test bundle id as well? Or for a wildcard bundle id? xcodebuild-test-without-building.log

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 “XXX.***.***” 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'm setting up a first workflow in Xcode Cloud and when I go through the flow and reach the 'Grant Access to your source code' pane, my projects repo is listed as primary and has a green checkmark next to it, but one of my SPM dependencies does not. When I press the 'Grant Access' it launches AppStoreConnect which complains the repo can't be found or I don't have the correct admin permissions. I'm using BitBucket Cloud and both repos are mine and I am the admin for both. Xcode itself will build the dependency locally correctly. I did see that the dependent SPM package needs a Package.resolved checked in, which I've now done, but I can still no longer get past the Grant Access step. When I try to add myself as admin to the dependent repo, BitBucket says I can't be added because I'm already an admin. This is the same for the projects primary repo as well. But Xcode still thinks I only have read access. How do I get passed this? Xcode isn't even telling me what repo is troublesome: { "category" : "xcode-cloud-data", "column" : "23", "subsystem" : "com.apple.dt.XcodeCloudKit", "details" : "Error alert: You must have Admin or Write access to your repository. Your current permission level is read.: ModelErrorResponseError(error: XcodeCloudAPI.Components.Schemas.ErrorResponse(message: \"You must have Admin or Write access to your repository. Your current permission level is read.\", errorKey: nil, helpUrl: nil, details: [], body: nil, actions: []), httpStatus: XcodeCloudCombineAPI.LegacyHttpStatus.badRequest, traceId: Optional(\"ee71bf64b8cf2c27\"), requestUrl: Optional(https:\/\/appstoreconnect.apple.com\/ci\/api\/teams\/69a6de89-4b61-47e3-e053-5b8c7c11a4d1\/products-v2\/A80C7CA9-25F0-4DCA-B7CC-D789A5022B88))\nError Description: Optional(\"You must have Admin or Write access to your repository. Your current permission level is read.\")\nRecovery Suggestion: nil\nHelp Anchor: nil", "createdAt" : "2025-06-28T18:49:15Z", "level" : "info", "filename" : "Logger+Additions.swift", "funcName" : "logError(_:)", "line" : "36" },

Dear all, For an important client, we are currently experiencing issues related to performance IOS build using Xcode Cloud. More in detail, their build process is taking approximately 30 minutes to complete at the moment, whereas the same build executed locally on a Mac machine takes around 7 minutes. This significant difference in build times is causing concerns and slowing down the development work. We would appreciate your support in identifying possible causes and exploring different ways to improve the actual situation (ex if it is possible to increase the Cloud machine calculation power). Could you please advise us on how we might proceed to analyze and potentially optimize the build times on Xcode Cloud? What kind of processors are used? Any guidance, best practices, or diagnostic steps you can suggest would be greatly appreciated. Looking forward to your support.

I am experiencing an issue where Xcode Cloud is not available in my Apple Developer Program account on App Store Connect. Despite having an active developer membership, I cannot access or enable Xcode Cloud for my apps. Could you please assist me in understanding why this feature is not available for my account and what steps I need to take to enable it?

I struggling in getting Xcode Cloud to work with a stand alone watch app. This app has the following three targets and each bundle identifier is set up in the Identifiers section of the developer portal. iphone container target called Unleashed abc.xyz.Unleashed watch target called Unleashed Watch App abc.xyz.Unleashed.watchkitapp watch target called Unleashed WidgetExtension abc.xyz.Unleashed.watchkitapp.Unleashed-Widget I have a App Store provisioning set up for abc.xyz.Unleashed.watchkitapp The app runs fine in the watch simulator, but fails with the following when I do an Xcode Cloud build Export archive for ad-hoc distribution Export archive for development distribution Export archive for app-store distribution When I expand each one of these errors it reports: Command exited with non-zero exit-code: 70 I also tried archiving the project in Xcode then selected the Archive but it won't let me validate because that button is disabled. Very confused I have successfully used Xcode Cloud for a phone app but am having a problem with this watch app that has a widget

I've been running into issues with Xcode Cloud/my workflow when it's trying to archive the app. I've tested locally and both archiving and building the app for release works. I've tried a few things to clear it. pod deintegrate and pod install Checking off "archive" for the build scheme Creating a certificate for both development and distribution. I made sure automatic signing was enabled as well. I have a ci_scripts/ci_post_clone.sh script that successfully completes. Have tried setting the xcode version of the workflow to 16.2 which is what my local xcode version is. I've switched it back to the latest, 16.4. running pod update Updating flutter However, I consistently get the following 2 errors : `Showing All Messages 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/resultBundleStreame3592434-5b88-48da-a3c4-f750abee4d08.json -IDEPostProgressNotifications=YES CODE_SIGN_IDENTITY=- AD_HOC_CODE_SIGNING_ALLOWED=YES CODE_SIGN_STYLE=Automatic DEVELOPMENT_TEAM=JG794CQD68 COMPILER_INDEX_STORE_ENABLE=NO -hideShellScriptEnvironment' ` and Showing All Messages Unhandled exception: ProcessException: No such file or directory Command: /Users/local/flutter/bin/flutter assemble --no-version-check --output=/Volumes/workspace/DerivedData/Build/Intermediates.noindex/ArchiveIntermediates/Runner/BuildProductsPath/Release-iphoneos/ -dTargetPlatform=ios -dTargetFile=lib/main.dart -dBuildMode=release -dConfiguration=Release -dIosArchs=arm64 -dSdkRoot=/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS18.5.sdk -dSplitDebugInfo= -dTreeShakeIcons=true -dTrackWidgetCreation=false -dDartObfuscation=false -dAction=install -dFrontendServerStarterPath= --ExtraGenSnapshotOptions= --DartDefines=RkxVVFRFUl9WRVJTSU9OPTMuMzUuMQ==,RkxVVFRFUl9DSEFOTkVMPXN0YWJsZQ==,RkxVVFRFUl9HSVRfVVJMPWh0dHA6Ly9naXRodWIuY29tL2ZsdXR0ZXIvZmx1dHRlci5naXQ=,RkxVVFRFUl9GUkFNRVdPUktfUkVWSVNJT049MjBmODI3NDkzOQ==,RkxVVFRFUl9FTkdJTkVfUkVWSVNJT049MWU5YTgxMWJmOA==,RkxVVFRFUl9EQVJUX1ZFUlNJT049My45LjA= --ExtraFrontEndOptions= -dSrcRoot=/Volumes/workspace/repository/ios -dTargetDeviceOSVersion= -dCodesignIdentity=- release_ios_bundle_flutter_assets #0 _ProcessImpl._runAndWait (dart:io-patch/process_patch.dart:519:7) #1 _runNonInteractiveProcessSync (dart:io-patch/process_patch.dart:686:18) #2 Process.runSync (dart:io-patch/process_patch.dart:79:12) #3 Context.runSyncProcess (file:///Users/local/flutter/packages/flutter_tools/bin/xcode_backend.dart:154:20) #4 Context.runSync (file:///Users/local/flutter/packages/flutter_tools/bin/xcode_backend.dart:118:34) #5 Context.buildApp (file:///Users/local/flutter/packages/flutter_tools/bin/xcode_backend.dart:539:34) #6 Context.run (file:///Users/local/flutter/packages/flutter_tools/bin/xcode_backend.dart:51:9) #7 main (file:///Users/local/flutter/packages/flutter_tools/bin/xcode_backend.dart:17:5) #8 _delayEntrypointInvocation.<anonymous closure> (dart:isolate-patch/isolate_patch.dart:312:33) #9 _RawReceivePort._handleMessage (dart:isolate-patch/isolate_patch.dart:193:12) Command PhaseScriptExecution failed with a nonzero exit code Any help here would be greatly appreciated.

We have had 2 Builds so far stuck archiving. Both indicate in their logs that Build Archive took a normal amount of time (9m and 19m) but the step Archive - iOS never finished. One of them ran for more than 6 days until we noticed and canceled it. The other one ran for 18 hours, and also had to be canceled manually. They were in two different projects, with no significant changes. The first build ran on Xcode 16.4 (16F6) and macOS Sequoia 15.6 (24G84), which we had had no issues like this with until just now, and the second ran on Xcode 26 (17A324) and macOS Tahoe 26 (25A354). We tested our app on the newest Xcode version and had no issues. Submitted report using feedback assistant: FB20279737.

Hi everyone, After opting out of Xcode Cloud, I tried to set it up again for my product. However, I’m getting the following message when attempting to reconnect to my source control provider: "Connecting Xcode Cloud with your source control provider was incomplete. Products cannot be configured to use Xcode Cloud while your team’s opt-out request is being processed." It’s been 7 days since I opted out, and I still haven’t been able to re-enable Xcode Cloud. I’ve tried reconnecting both GitHub and Bitbucket, but the same message appears in both cases. I’d like to know: How long does the opt-out (deregistration) process usually take to complete? Is there any way to check the current status or expedite the reactivation process? Team Type: Organization Region: Japan Any insights or similar experiences would be greatly appreciated. Thank you in advance!

After a break using AWS Macs for CI we are willing to give Xcode cloud another go. Unfortunately we are unable to complete the "Grant Access to your Source Code" step. We tried multiple accounts including maintainer, owner and admin. We tried from multiple Macs and versions of macOS. "Connecting Xcode Cloud with your source control provider was incomplete. 503 Service Unavailable. Please ensure that your repository is available and accepting connections."

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

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