I am experimenting with Swift Testing and Xcode Cloud and would like to write some tests that require to use MusicKit functionality. For example I'd like to fetch an album via MusicCatalogRessourceRequest to test an initializer of another struct.
However this test fails because the permission to access the music library is not granted. Once the permission is granted, the test works as expected.
Things I have tried:
Add NSPrivacyAccessedAPITypes to the Info.plist. This did not show any effect. Below is the corresponding snippet
Trying to tap the button programmatically. Once again this did not show any effect.
The Info.plist snippet:
<key>NSPrivacyAccessedAPITypes</key>
<array>
<string>NSPrivacyAccessedAPIMediaLibrary</string>
</array>
The code snippet to tap the button:
let systemAlerts = XCUIApplication(bundleIdentifier: "com.apple.springboard")
let allowButton = systemAlerts.buttons["Allow"]
if allowButton.exists {
allowButton.tap()
}
What am I doing wrong here? I need access to MusicKit functionalities to write meaningful tests. Thank you
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.
Posts under Xcode Cloud tag
155 Posts
Sort by:
Post
Replies
Boosts
Views
Activity
A local build will take ~2 minutes to build. But the same build will take 15 min at least on Xcode Cloud. Can anything be done here?
I'm trying to set up Xcode Cloud for the first time. When I go through the "Get Started" flow and get to "Grant Access to Your Source Code" step, when I click the "Grant Access" button, I get "This Operation Could Not Be Completed."
It has the correct URL to my Github repo.
Github is working fine in Xcode itself: I can push and pull changes and view repo history.
I've tried:
restarting Xcode
rebooting the Mac
Removing the Github account from Xcode and adding it back
Creating a new Github personal token and removing the Github account from Xcode and using the new token to add it back
I've looked through my Github settings and don't see anything that might cause an issue.
I filed FB16511549 to report this. The error dialog in Xcode automatically filled the feedback fields, and says:
"API Invalid status code: 500. XcodeCloudCombineAPI.XCCResponseError:1"
I'm running Xcode 16.2 (16C5032a) on an M4 MacBook Pro running Sequoia 15.3.1 (24D70).
Does anyone have any insights or ideas of other things to try?
Thanks.
I am setting up a new app and am having problems with Xcode Cloud. From Xcode if I click on the "Cloud" button under the Report Navigator I get a spinner for a long time then get the message "Could not load Xcode Cloud data". I also visited the "Xcode Cloud" tab under my app in App Store Connect and I get a spinner and nothing loads.
This is a recent account and I'm setting up Xcode Cloud for the first time. Below is what I've tried and I'm out of ideas on how to get this working.
In Xcode, I signed out and back in as the Account Holder
Closed Xcode and reopened
This occurred yesterday and today and have not seen a problem under the Apple System Status page
On the latest Xcode 16.2
Checked the Signing & Capabilities tab in Xcode and my team a bundle Id is correct and it's happy with signing. At this time on my machine I am using the distribution profile.
Hi,
We have an app that is a default mail client, so it has this entry in its entitlements file: com.apple.developer.mail-client. This seems to create issues with ad-hoc distribution.
We can distribute the app on App Store Connect without any issues and have been doing so for a while.
We wanted to try using Xcode Cloud to manage our releases. The app export works fine for both App Store Distribution and Development Distribution.
However, the ad-hoc distribution step fails. (We don't need ad-hoc distribution, but Xcode Cloud seems to prevent us from removing this step.)
I tried building and releasing the app locally for ad-hoc distribution and encountered the same error as on Xcode Cloud.
When Xcode tries to generate the profile, it outputs the following error:
Provisioning profile "iOS Team Ad Hoc Provisioning Profile: com.infomaniak.mail" failed qualification checks:
Profile doesn't support Default Mail App.
Profile doesn't include the com.apple.developer.mail-client entitlement.
Is it something broken with our config ? What are we missing ?
Local error in Xcode Organizer:
Remote error on Xcode cloud:
Hello, my app has a custom font for some UI elements. When building with XCODE to my local device, all works and looks great. When distributing with TestFlight, the font doesn't seem to apply!
Yes, I've included the .ttf in my Development assets, anyone else having this issue with the TestFlight Distribution of their app?
Hi,
I have a project that integrates the Firebase SDK via SPM as a dependency of an internal Swift Package:
My app ⟶ My Library ⟶ Firebase SDK
The project builds successfully and can be archived locally ✅. The uploaded .ipa is valid and gets published 🚀.
However, we are now trying to automate the release process using Xcode Cloud, but the iOS Archive action is failing ❌ on Xcode Cloud.
The logs show the following error ⬇️:
error: exportArchive codesign command failed (/Volumes/workspace/tmp/XcodeDistPipeline/XcodeDistPipeline.~~~oomCvM/Root/Payload/base-ios.app/Frameworks/FirebaseAnalytics.framework: replacing existing signature
/Volumes/workspace/tmp/XcodeDistPipeline/XcodeDistPipeline.~~~oomCvM/Root/Payload/base-ios.app/Frameworks/FirebaseAnalytics.framework: invalid or corrupted code requirement(s)
Requirement syntax error(s):
line 1:178: unexpected token: <COMPANY_NAME>
)
** EXPORT FAILED **
I have been researching this issue for a while and have tried several solutions to fix it, but with no luck. Even though the error points to a specific library—the Firebase SDK—I don’t believe Firebase is the root cause. There were related issues in the past, but those were already fixed by the Firebase team, and as I mentioned, the project archives correctly when built locally.
On the other hand, the error states:
line 1:178: unexpected token: <COMPANY_ACRONYM>
This makes me wonder if there’s an issue parsing our Team Name during the re-signing process, as it contains special characters ":
"name": "Apple Distribution: Company Full Name "COMPANY_ACRONYM""
Hi everyone,
We're developing a mobile app with Flutter and I linked my GitHub with XCode Cloud. This is the first time we're using XCode Cloud and we are struggling with the build, they fail every time.
A little context, we started by adding the ci_post_clone.sh script, then adding a few files in the versioning, etc...
Now it looks like the build is going through be we are facing issues with the part:
Scan dependencies of GeneratedPluginRegistrant.m
It's throwing an error: Module 'cloud_firestore' not found, even though the module is installed before by performing a pod install.
It's building locally on both Flutter with IntelliJ and XCode, we tried several times to flutter clean or pod deintegrate but nothing works!
Any clue?
Thanks,
Hello,
I submitted a request to migrate my developer membership from individual to organization over 6 days ago. Before submitting this request I was told it was a "quick process".
When I ask for updates, all I get is "we have confirmed that the team is continuing to review your case and we will contact you again once they have provided an update." I never get any said updates.
Not only can I not submit my app, I've been locked out of TestFlight, meaning I haven't been able to send the app to beta testers.
I'm curious, has anyone done this migration and how long did it take?
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 have a working Xcode Cloud setup for my iOS and macOS targets, and I'm trying to add visionOS support. The issue is that Firebase requires using their source distribution for visionOS (instead of their default binary distribution).
Locally, this works by launching Xcode with:
open -a Xcode --env FIREBASE_SOURCE_FIRESTORE project.xcodeproj
For Xcode Cloud, I've added a ci_post_clone.sh script that sets this environment variable for visionOS builds:
#!/bin/bash
if [[ $CI_PRODUCT_PLATFORM == "xrOS" ]]; then
echo "Running setup for visionOS..."
export FIREBASE_SOURCE_FIRESTORE=1
fi
However, I'm getting the following error during build:
an out-of-date resolved file was detected at /.../project.xcworkspace/xcshareddata/swiftpm/Package.resolved, which is not allowed when automatic dependency resolution is disabled
So since setting FIREBASE_SOURCE_FIRESTORE=1 changes which SPM dependencies are required:
Normal setup uses: abseil-cpp-binary, grpc-binary
Source distribution needs: abseil-cpp-swiftpm, grpc-ios, boringssl-swiftpm
What's the recommended way to handle this in Xcode Cloud when maintaining builds for all platforms? Should I be using separate workflows with different branches for different platforms? Or is there a better approach?
System:
Xcode 16.2
Using SPM for dependency management
Firebase iOS SDK 10.29.0
Building for iOS, macOS, and visionOS
Thanks in advance for any guidance!
Am I understanding correctly that Xcode Cloud still does not support Metal in 2025?
After changing the bundle identifier of my app, I’ve encountered several issues that I can’t seem to resolve, even though I’ve followed all the necessary steps. The app with the previous identifier was live on Testflight, and working perfectly fine, but now I’m facing the following problems:
WeatherKit Authentication Issue
WeatherKit has stopped working, and I’m getting authentication errors. I’ve updated the app in the Developer Portal to reflect the new bundle ID, but it still doesn’t authenticate properly.
Xcode Cloud Configuration Issue:
Xcode is asking me to set up Xcode Cloud again, which I understand is expected after a bundle ID change. However, during the setup process, it fails to recognize my remote repository, even though the repository is correctly added and visible under the Source Control tab.
TestFlight Internal Testing Issue:
I manually uploaded a build to TestFlight, but internal testers cannot use it because the invitation appears as invalid. This wasn’t an issue with the app’s previous identifier.
It seems like the bundle ID change has caused some fundamental issues that I can’t resolve despite following all the usual instructions. Has anyone experienced this before or knows how to resolve these problems?
I'm using the latest Xcode 16.2 on Mac OS Sequoia 15.2
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.
All tests build and run locally just fine. Xcode Cloud can build my code, but always fails to run tests with the below errors. How can I even begin to troubleshoot this?
I think my setup is pretty straightforward. Just a simple test plan that execute some unit tests with Swift Testing.
Run command: 'xcodebuild test-without-building -destination 'platform=iOS Simulator,id=1EB80431-1A0B-4AD8-8EA6-968EA09C3F23' -resultBundleVersion 3 -resultBundlePath /Volumes/workspace/resultbundle.xcresult -resultStreamPath /Volumes/workspace/tmp/resultBundleStream679e7ce9-a095-4be5-8dfa-4c9df982e547.json -IDEPostProgressNotifications=YES -DTDKDisableSymbolCopying=YES -test-timeouts-enabled YES -maximum-test-execution-time-allowance 1800 -hideShellScriptEnvironment -maximum-parallel-testing-workers 8 -testProductsPath /Volumes/workspace/TestProducts.xctestproducts'
(6378) encountered an error (Early unexpected exit, operation never finished bootstrapping - no restart will be attempted. (Underlying Error: Test crashed with signal ill before starting test execution.))
May be related to:
https://developer.apple.com/forums/thread/725660
Issue with "Mine" Branch Not Displaying After Switching GitHub Accounts in XcodeCloud
I have been using XcodeCloud for a while. Recently, in one of my projects, I switched from using my personal GitHub account to a separate GitHub account for work purposes. Since then, when I manually start a workflow, nothing is displayed under the "Mine" section on the branch selection screen.
I suspect that Xcode is attempting to list branches from the previously used account, causing branches from my new account not to appear. Where are these old account settings stored, and how can I reset them?
For reference:
In Xcode's Accounts settings, only the new GitHub account is present—the old account is no longer listed.
The git user in the local repository has also been updated to the new one.
Any assistance on how to resolve this issue would be greatly appreciated!
Currently Im trying to save few files in it but on every run this folder is empty. I have the following script in ci_post_clone.sh
mkdir ${CI_DERIVED_DATA_PATH}
cd ${CI_DERIVED_DATA_PATH}
ls -als
touch test
return 1
My expectation is that on the second run it would show test file in DerivedData or fail at creating the directory, but the issue is that this file is not created.
does it need a successful build for this folder to be saved? in Xcode Cloud, in workflow environment I have unchecked Clean build Xcode Cloud will not restore derived data or caches for your builds, which may take significantly longer as a result.. One more question here would be what is meant by caches? are there other folders being saved?
Also a bit of context. Im trying to build a Kotlin Multiplatform project but it fails with
Showing All Issues
> Could not resolve all files for configuration ':composeApp:iosArm64CompileKlibraries'.
> Could not download lifecycle-viewmodel.klib (androidx.lifecycle:lifecycle-viewmodel-iosarm64:2.9.0-alpha03)
> Could not get resource 'https://dl.google.com/dl/android/maven2/androidx/lifecycle/lifecycle-viewmodel-iosarm64/2.9.0-alpha03/lifecycle-viewmodel-iosarm64-2.9.0-alpha03.klib'.
> Could not GET 'https://dl.google.com/dl/android/maven2/androidx/lifecycle/lifecycle-viewmodel-iosarm64/2.9.0-alpha03/lifecycle-viewmodel-iosarm64-2.9.0-alpha03.klib'.
> Got socket exception during request. It might be caused by SSL misconfiguration
> Connection reset by peer
my guess is that Xcode Cloud or Google servers probably has some limitation. So if I cache those libraries my project will hopefuly compile once again.
In previous versions, strokeWidth and strokeColor were set, and now there will be raised lines inside the border
how to fix it
Hi,
I'm trying to register the application with Xcode Cloud.
For that, I click on the "cloud" button in Xcode.
First steps goes OK, but it fails at "create App on App Store Connect"
The error is Cannot register the product
Usually, I change the bundle name, but this time it gets weird, as Xcode managed to create the Identifier, as it is not taken.
So the identifier is created in the developer portal but it fails anyway.
I also tried to create the app directly in the portal, and it works, therefore the app name is not the problem.
Then I delete the app and try again with Xcode and it fails...
Any solution for this issue please?
Hi there, it seems like the "Latest Release" option for Xcode Cloud's environment settings has rev'd to 16.2 (16C5032) (since yesterday?) but is causing Mac Catalyst archives to fail with the error "This bundle is invalid. Apple is not currently accepting applications built with this version of Xcode." iOS and tvOS builds are archiving as expected, but this is blocking my deployment.
I would have expected "Latest Release" to always result in a version that is accepted for deployment - am I doing something wrong?
My settings for my deployment workflow are below: