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.
Post
Replies
Boosts
Views
Activity
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?
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.
Xcode 16.2 Framework Signing Issues with Cloud Managed Developer ID in Automated Builds
Issue Description
After upgrading from Xcode 15.4 to 16.2, our macOS app's frameworks are failing notarization with the error "The binary is not signed with a valid Developer ID certificate" for embedded frameworks when building through fastlane. This worked correctly in Xcode 15.4. Importantly, manually archiving and notarizing through the Xcode GUI still works correctly - the issue only occurs during automated builds.
Build Configuration
We use fastlane to build and notarize our macOS app:
build_mac_app(
scheme: 'Runner',
export_method: "developer-id",
xcargs: '-allowProvisioningUpdates'
)
This generates the following xcodebuild commands:
Archive:
xcodebuild -workspace ./Runner.xcworkspace -scheme Runner -destination 'generic/platform=macOS' -archivePath /path/to/archive -allowProvisioningUpdates archive
Export with plist:
xcrun -exportArchive -exportOptionsPlist '/path/to/plist' -archivePath /path/to/archive -exportPath '/output/path' -allowProvisioningUpdates
Export options plist contents:
&lt;?xml version="1.0" encoding="UTF-8"?&gt;
&lt;!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"&gt;
&lt;plist version="1.0"&gt;
&lt;dict&gt;
&lt;key&gt;installerSigningCertificate&lt;/key&gt;
&lt;string&gt;Developer ID Installer: Company Inc (1234567891)&lt;/string&gt;
&lt;key&gt;method&lt;/key&gt;
&lt;string&gt;developer-id&lt;/string&gt;
&lt;key&gt;signingStyle&lt;/key&gt;
&lt;string&gt;automatic&lt;/string&gt;
&lt;/dict&gt;
&lt;/plist&gt;
Notarization:
ditto -c -k --rsrc --keepParent "My App.app" "My App.app.zip"
xcrun notarytool submit "My App.app.zip" --output-format json --wait --key /path/to/key --key-id ABCDEFGHIJ --issuer 12345678-abcd-1234-5678-fc2d96b1735a
Error Output
Notarization fails with the following errors:
{
"severity": "error",
"code": null,
"path": "My App.app.zip/My App.app/Contents/Frameworks/some_package.framework/Versions/A/some_package",
"message": "The binary is not signed with a valid Developer ID certificate.",
"docUrl": "https://developer.apple.com/documentation/security/notarizing_macos_software_before_distribution/resolving_common_notarization_issues#3087721",
"architecture": "arm64"
}
Key Details
Using Xcode Cloud managed Developer ID certificates (not local certificates)
✅ Building, archiving, and notarizing through Xcode GUI works correctly
Automatic signing is enabled
Expected Behavior
Frameworks should be automatically signed with the cloud managed Developer ID certificate during the export process, as they were in Xcode 15.4.
Has there been a change in how framework signing is handled with cloud managed certificates in Xcode 16.2's command line tools? Any guidance on how to ensure frameworks are properly signed during automated builds when using automatic signing with cloud managed Developer ID certificates would be appreciated.
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,
I have an app I am toying with and I am seeing the following error in github's Xcode automation from Apple. My other apps work fine fine in xcode cloud with the same project setup.
Run scheme_list=$(xcodebuild -list -json | tr -d "\n")
2025-02-05 03:15:56.669 xcodebuild[2841:17672] Writing error result bundle to /var/folders/2s/h6hvv9ps03xgz_krkkstvq_r0000gn/T/ResultBundle_2025-05-02_03-15-0056.xcresult
xcodebuild: error: Unable to read project 'Legacy Letters.xcodeproj'.
Reason: The project ‘Legacy Letters’ cannot be opened because it is in a future Xcode project file format (70). Adjust the project format using a compatible version of Xcode to allow it to be opened by this version of Xcode.
/opt/homebrew/Cellar/ruby@3.0/3.0.7/lib/ruby/3.0.0/json/common.rb:216:in `parse': 809: unexpected token at '' (JSON::ParserError)
from /opt/homebrew/Cellar/ruby@3.0/3.0.7/lib/ruby/3.0.0/json/common.rb:216:in `parse'
from -e:1:in `<main>'
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!
I get this error:
Verification failed with status INVALID_APP_IDENTIFIER
we use this method:
payload = signed_data_verifier.verify_and_decode_notification(notification_data)
I use Production environment (this is automatically set in our server) and use my device (connected to Mac) to test the purchase. When trying to purchase I get the Sandbox environment in the Widget.
This works when manually setting the environment to Sandbox before calling the function. The time it works because it does not check the apple app id (because of the environment).
Now my question is: Which is the apple app id? Is it the App Id "Apple-ID" in the app store connect? Or is it the TeamId+BundleId?
Could it be that my function doesnt work because the Payment was done in Sandbox and the environment is Production?
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
We are encountering build failures during the following stages on Xcode Cloud:
• Export archive for ad-hoc distribution -> fail
• Export archive for development distribution -> fail
• Export archive for app-store distribution -> fail
Run command: 'xcodebuild -exportArchive -archivePath /Volumes/workspace/tmp/a603f613-f0a2-4053-9316-2f25ca93250d.xcarchive -exportPath /Volumes/workspace/adhocexport -exportOptionsPlist /Volumes/workspace/ci/ad-hoc-exportoptions.plist '-DVTPortalRequest.Endpoint=http://172.16.56.69:8089' -DVTProvisioningIsManaged=YES -IDEDistributionLogDirectory=/Volumes/workspace/tmp/ad-hoc-export-archive-logs -DVTSkipCertificateValidityCheck=YES -DVTServicesLogLevel=3'
Error
Command exited with non-zero exit-code: 70
2025-01-21T05:11:20.962717086Z error: exportArchive There is a problem with the request entity
2025-01-21T05:11:20.962756880Z
2025-01-21T05:11:20.962760011Z error: exportArchive No signing certificate "iOS Distribution" found
2025-01-21T05:11:20.962764378Z
2025-01-21T05:11:20.962767137Z error: exportArchive There is a problem with the request entity
2025-01-21T05:11:20.962771440Z
2025-01-21T05:11:20.962774232Z error: exportArchive No signing certificate "iOS Distribution" found
The build process was functioning correctly until this morning with same branch. We also have verified that our certificates are valid and successfully uploaded to TestFlight using these certificates on the local Xcode environment.
This appears to be an issue on the Xcode Cloud side as no significant configuration changes were made on our end.
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 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.
Our UITests are failing because Simulator won't start up. What can I do here?
Workflow Settings:
Sequoia 15.1
Xcode 16.1
Testing on iPad and iPhone 17.5 simulators
Thank you in advance
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
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,
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.