Hello,
Has anyone used Sentry with Xcode Cloud? How are you uploading dSYM files? One way is fastlane but Xcode Cloud doesn't come with Fastlane preinstalled, the other is sentry-cli but the same issue, it's not preinstalled.
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.
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
Recently, I have trouble with my Xcode Cloud builds, where they seemingly complete, but the very final step does not happen.
I am building from the same codebase for both macOS and iOS (I have two “Archive” steps in my workflow, one for iOS and one for macOS). The iOS one usually completes fast without problems. The macOS log ending looks like this, and remains stuck forever, with the macOS build in the “spinning progress” state and never completing.
Is there something I can do on my end to make this work better? I would not want to go back to manual builds, Xcode Cloud is convenient and was working well for a while, but this is really annoying lately.
Hi,
Overview
I am using Xcode Cloud for my multi platform app.
The macOS test case fails, however the iOS test case runs and succeeds.
I don't have any UI test cases written, the test case are simple and have nothing platform (macOS) specific.
Questions
What can I do to fix this?
Is there any user privileges needed to launch the macOS app for testing? I ask because when I ran the UI tests locally it launched the app and asked for my macOS user password. Just wondering if that is the reason it didn't launch in Xcode Cloud.
Error:
<Appname> encountered an error (Failed to install or launch the test runner. If you believe this error represents a bug, please attach the result bundle at /Volumes/workspace/resultbundle.xcresult.(Underlying Error: Could not launch "AppnameTests. The LaunchServices launcher has returned an error. Please check the system logs for
the underlying cause of the error. (Underlying Error: The operation couldn't be completed. Launch failed. (Underlying Error: Launch job spawn failed) )))
× Could not launch "<Appname>"
× Could not launch "AppnameTests"
× AppnameUITests.testExample()
Failed to get launch progress for <XCUIApplicationImpl: 0x600000564630 <BundleID> at /Volumes/workspace/TestProducts/Debug-Dev/<Appname>.app>: Could not launch "app name". The LaunchServices launcher has returned an error. Please check the system logs for the underlying cause of the error. (Underlying Error: The operation couldn't be completed. Launch failed. (Underlying Error: Launch job spawn failed))
AppnameUITests.swift:28
* AppnameUITests.testLaunchPerformance)
Failed to get launch progress for «XCUIApplicationimpl: 0x60000054630 <BundleID> at /Volumes/workspace/TestProducts/Debug-Dev/<Appname>.apps: Could not launch "<Appname>". The LaunchServices launcher has returned an error. Please check the system logs for the underlying cause of the error. (Underlying Error: The operation couldn't be completed. Launch failed. (Underlying Error: Launch job spawn failed))
AppnameUITests.swift:37 g
* AppnameUITestsLaunchTests.testLaunch)
Failed to get launch progress for «XCUIApplicationimpl: 0x60000054630 <BundleID> at /Volumes/workspace/Testroducts/Debug-Dev/<Appname>.apps: Could not launch "<Appname>". The LaunchServices launcher has returned an error. Please check the system logs for the underlying cause of the error. (Underlying Error: The operation couldn't be completed. Launch failed.
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?
Xcode Cloud always exports archive using ad-hoc, development and app-store profiles. This uses up 5-6 more minutes always for my app. How to disable and allow export only in single distribution profile
Topic:
Developer Tools & Services
SubTopic:
Xcode Cloud
Tags:
Signing Certificates
Xcode Cloud
wwdc2023-10224
wwdc2023-10278
When running a SwiftUI Multiplatform app in Xcode Cloud I'm getting the following error:
CIWatcher encountered an error in CIWatcherTests failed with:
Failed to install or launch the test runner. (Underlying Error: Could not launch “CIWatcherTests”. 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)))
This runs fine on iOS and all those tests pass.
The SwiftUI app on Mac is a menu bar app so I'm not sure if this could be the issue as it's not launching for some reason on the Xcode Cloud system? Maybe I need to add some run option to make this work?
When run locally both iOS and macOS pass all the tests successfully
Hi, recently something happened in Xcode Cloud, and the build times increased massively. In our CI workflow we run test, and one of the phases executes xcodebuild build-for-testing: the duration of this phase moved from about 8 minutes to about 36 minutes, without any major changes on our side.
We observed this:
in different apps;
even when running a build on a old tag.
All other phases don't seem affected, it's just the xcodebuild build-for-testing phase.
I'm attaching 2 screenshots of the logs from AppStoreConnect that show the duration of each phase, where build 7600 is older and 7700 is more recent (but was run on a tag from a few weeks ago, to exclude issues related with the code base itself).
We had not other option than to disable the CI checks for PRs, because they would take too long, and use up too much of Xcode Cloud time.
What's happening?
Thanks
Topic:
Developer Tools & Services
SubTopic:
Xcode Cloud
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
After trying to build with macOS 15 and XCode 16 (beta and beta2), XcodeCloud started to crash at the Resolve package dependencies step.
Everything works perfect on my local system running same OS same XC.
Details: [<IDESwiftPackageCore.IDESwiftPackageDependencyPlaceholderFileReference, 0x7fb23a2082a0: name:swift path:(No Path)>]
Function: unregisterDependencyFileReferences(_:)
Thread: <_NSMainThread: 0x600002094200>{number = 1, name = main}
Hints:
Backtrace:
0 -[DVTAssertionHandler handleFailureInFunction:fileName:lineNumber:assertionSignature:messageFormat:arguments:] (in DVTFoundation)
1 _DVTAssertionHandler (in DVTFoundation)
2 _DVTAssertFromSwift (in DVTFoundation)
3 _DVTAssert(_:file:line:function:varargs:) (in DVTFoundation)
4 DVTAssert(_:_:file:line:function:) (in DVTFoundation)
5 closure #1 in closure #1 in IDESPMWorkspaceDelegate.unregisterDependencyFileReferences(_:) (in IDESwiftPackageCore)
6 closure #1 in IDESPMWorkspaceDelegate.unregisterDependencyFileReferences(_:) (in IDESwiftPackageCore)
7 closure #1 in OS_dispatch_queue.dvt_sync<A>(execute:) (in DVTFoundation)
8 thunk for @callee_guaranteed () -> () (in DVTFoundation)
9 thunk for @escaping @callee_guaranteed () -> () (in DVTFoundation)
10 -[DVTModelObjectGraph performBlockCoalescingModelChanges:] (in DVTFoundation)
11 DVTModelObjectGraph.performBlockCoalescingModelChanges<A>(_:) (in DVTFoundation)
12 IDESPMWorkspaceDelegate.unregisterDependencyFileReferences(_:) (in IDESwiftPackageCore)
13 closure #1 in closure #1 in IDESPMWorkspaceDelegate.registerDependencyFileReferences(_:) (in IDESwiftPackageCore)
14 closure #1 in IDESPMWorkspaceDelegate.registerDependencyFileReferences(_:) (in IDESwiftPackageCore)
15 closure #1 in OS_dispatch_queue.dvt_sync<A>(execute:) (in DVTFoundation)
16 thunk for @callee_guaranteed () -> () (in DVTFoundation)
17 thunk for @escaping @callee_guaranteed () -> () (in DVTFoundation)
18 -[DVTModelObjectGraph performBlockCoalescingModelChanges:] (in DVTFoundation)
19 DVTModelObjectGraph.performBlockCoalescingModelChanges<A>(_:) (in DVTFoundation)
20 IDESPMWorkspaceDelegate.registerDependencyFileReferences(_:) (in IDESwiftPackageCore)
21 closure #1 in IDESPMWorkspaceDelegate.dependencyPackagesDidUpdate(packages:graphHasErrors:) (in IDESwiftPackageCore)
22 closure #1 in OS_dispatch_queue.dvt_sync<A>(execute:) (in DVTFoundation)
23 thunk for @callee_guaranteed () -> () (in DVTFoundation)
24 thunk for @escaping @callee_guaranteed () -> () (in DVTFoundation)
25 __58-[DVTModelObjectGraph performBlockCoalescingModelChanges:]_block_invoke (in DVTFoundation)
26 -[DVTModelGraphTransactionScope performTransaction:] (in DVTFoundation)
27 -[DVTModelObjectGraph performBlockCoalescingModelChanges:] (in DVTFoundation)
28 DVTModelObjectGraph.performBlockCoalescingModelChanges<A>(_:) (in DVTFoundation)
29 IDESPMWorkspaceDelegate.dependencyPackagesDidUpdate(packages:graphHasErrors:) (in IDESwiftPackageCore)
30 SPMWorkspace.packageGraphActionFinished(_:) (in SwiftPM)
31 closure #3 in SPMWorkspace.processPackageGraphActionsInBackgroundIfNeeded() (in SwiftPM)
32 swift::runJobInEstablishedExecutorContext(swift::Job*) (in libswift_Concurrency.dylib)
33 swift_job_runImpl(swift::Job*, swift::SerialExecutorRef) (in libswift_Concurrency.dylib)
34 _dispatch_main_queue_drain (in libdispatch.dylib)
35 _dispatch_main_queue_callback_4CF (in libdispatch.dylib)
36 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ (in CoreFoundation)
37 __CFRunLoopRun (in CoreFoundation)
38 CFRunLoopRunSpecific (in CoreFoundation)
39 +[DVTKVOConditionValidator waitForCondition:sourceObject:keyPathAffectingConditionBlock:timeout:] (in DVTFoundation)
40 -[Xcode3CommandLineBuildTool waitForRemoteSourcePackagesToFinishLoading] (in Xcode3Core)
41 -[Xcode3CommandLineBuildTool _resolveInputOptionsWithTimingSection:] (in Xcode3Core)
42 -[Xcode3CommandLineBuildTool run] (in Xcode3Core)
43 XcodeBuildMain (in libxcodebuildLoader.dylib)
44 -[XcodebuildPreIDEHandler loadXcode3ProjectSupportAndRunXcode3CommandLineBuildToolWithArguments:] (in xcodebuild)
45 -[XcodebuildPreIDEHandler runWithArguments:] (in xcodebuild)
46 main (in xcodebuild)
47 start (in dyld)
bash: line 1: 4274 Abort trap: 6 xcodebuild -resolvePackageDependencies -project /Volumes/workspace/repository/XXX.xcodeproj -scheme 'XXX' -derivedDataPath /Volumes/workspace/DerivedData -hideShellScriptEnvironment
Error
Command exited with non-zero exit-code: 134
Topic:
Developer Tools & Services
SubTopic:
Xcode Cloud
Tags:
Swift Packages
Developer Tools
Beta
Xcode Cloud
The answer to my question is probably very simple but I've spent twelve hours trying to find it myself and I am at my wit's end. Searching the web shows multiple sufferers from, and multiple answers to, this same problem from at least ten years ago.
I've a SwiftUI macOS/iOS app that is not finished but at a stage where I want to get it ready for TestFlight. I set it up on App State Connect and set Xcode Cloud to build it on GitHub commits.
The first build revealed some obvious omissions, easily fixed, then I hit this one, for macOS: Missing required icon. The application bundle does not contain an icon in ICNS format, containing both a 512x512 and a 512x512@2x image.
[In passing, I'll note the app, passes muster for the iOS platform]
I make a 1024x1024 PNG .. convert it to ICNS with GraphicConverter .. convert it again with iconutil to a iconset and add it to my app. I do a regular build in Xcode and, there it is, my .icns file in the app bundle.
I commit to fire off another Xcode Cloud build, but get the same error. Especially frustrating because I can see the ".. application bundle does contain an icon in ICNS format, containing both a 512x512 and a 512x512@2x image".
It's hard to debug from an abundantly obvious incorrect diagnostic, but I do have to get past this and start fiddling with assorted settings .. ten builds later, still no joy.
I did notice that my Info.plist file (autogenerated) doesn't contain the string "icon" and that, for example, Mail.app has:
<key>CFBundleIconFile</key>
<string>ApplicationIcon</string>
<key>CFBundleIconName</key>
<string>ApplicationIcon</string>
If the build process checks for an icon based on the Info.plist contents then the reported error could be more correct, ".. application bundle's Info.plist file makes no reference to an icon in ICNS format .."
One possible complication is that my app includes embedded custom fonts and so it need a Fonts.plist file for them. I set that file as my INFOPLIST_FILE
<key>UIAppFonts</key>
<array>
<string>Zerlina.otf</string>
<string>Gorton-Condensed.otf</string>
<string>Gorton-Normal-180.otf</string>
<string>Gorton-Normal-120.otf</string>
</array>
<key>ATSApplicationFontsPath</key>
<string>.</string>
The contents of Fonts.plist are copied to the final Info.plist. Maybe that defeated some of the Info autogeneration? I see no setting for CFBundleIconFile so can't add it myself.
I'm confident pressing "Submit" on this will suddenly clear my mental murk but, for now, I need help .. thanks for any ..
Topic:
Developer Tools & Services
SubTopic:
Xcode Cloud
Tags:
App Store Connect
TestFlight
Xcode Cloud
I'm using Xcode Cloud for release builds and unit tests, and it works fine. Recently, I added some XCUITests, but to run it the way I need I started to use this mock server. Basically, the idea is you define before each test what responses you want to get for specific requests. It works like a charm locally. But if I want to run it in Xcode Cloud, it looks like the server has failed to launch. The mock server is a separately launched binary file. I think this is because this permission I get when launch it locally.
So, my question is how to allow this kind of permission in Xcode Cloud to make my UITests works correctly?
You can find a detailed instruction how server is launched on a github page I provided.
When exporting an archive....
NSLocalizedDescription=Communication with Apple failed, NSLocalizedRecoverySuggestion=A non-HTTP 200 response was received (504) for URL https://developerservices2.apple.com/services/QH65B2/listTeams.action?clientId=[redacted]
Topic:
Developer Tools & Services
SubTopic:
Xcode Cloud
I'm waiting over 1 hour 20 minutes to start build task
Topic:
Developer Tools & Services
SubTopic:
Xcode Cloud
We are experiencing an ongoing issue with Xcode Cloud where builds take up to 90 minutes to queue and then take more than the maximum timeout to finish, leading to an error. Typically the Test Actions will finish the xcodebuild command, but then fail to begin executing tests. No errors are displayed in the logs.
Hello!
I am new to creating workflows in Xcode cloud. I have a problem I'm trying to solve.
In my ci_post_clone script I trigger a job in github. I need to keep track of the generated id in order to shut down the job in my ci_post_xcodebuild script.
What is the best way to do that? I tried assigning to a env variable and outputting the value to a file but it seems like ci_post_xcodebuild runs in a fresh env and can't find my variable.
Any help would be really appreciated.
Hi, When a workflow is started, its taking more than an hour to start the actual archive and in all this time its stuck in the queue. When it starts after more than an hour, the archive is also taking more than 30 minutes and once this whole process reaches 2 hours, it just fails with this error,
Build has exceeded the maximum allotted time. Each build can run for up to 120 minutes. If a build has not yet finished at this time, all incomplete actions will be cancelled.
I have been using Xcode cloud for long time now but never experienced such behavior before. What is the issue?
We have all of our CD except for deploys in another provider for the moment. From that provider (Github Actions), we want to use the API to kick off a deploy/archive workflow. We're using the new manual start condition that gets called if everything else in our pipeline passes. However, it's not clear how to specify which branch to run the workflow on. I know you can get the ScmGitReference when the workflow is already running on a branch based off of other start conditions, but I want to allow the deploy to run on any branch, theoretically, and control whether the deploy workflow gets kicked off or not from my third-party location. How do I do this?
Hi,
There is a status check in XCode Cloud and I've been trying to upload new builds from local machine to testFlight.
Archive success
Uploading success
However TEST FLIGHT is not showing new builds.
Do you face such an issue ?
The Archive - iOS action could not complete due to an error. The error may not occur on rebuild.
I am using xcode cloud with version xcode 15.
I can build successfully but archive gets fail . Even don't getting any error. Please help me.Thanks in advance.
Hello, I am getting the following error in Xcode Cloud:
/Volumes/workspace/repository/macos/Runner.xcodeproj: error: No signing certificate "Mac Development" found: No "Mac Development" signing certificate matching team ID "22649D52Q5" with a private key was found. (in target 'Runner' from project 'Runner')
I have automatic signing turned on in Xcode and the program compiles/runs fine in Xcode.
Below is my ci_post_clone.sh script
#!/bin/sh
# Fail this script if any subcommand fails.
set -e
# The default execution directory of this script is the ci_scripts directory.
cd $CI_PRIMARY_REPOSITORY_PATH # change working directory to the root of your cloned (cloud) repo.
# Install Flutter using git.
git clone https://github.com/flutter/flutter.git --depth 1 -b stable $HOME/flutter
export PATH="$PATH:$HOME/flutter/bin"
# Install Flutter artifacts for iOS (--ios), or macOS (--macos) platforms.
flutter precache --macos
# Install Flutter dependencies.
flutter pub get
# Install CocoaPods using Homebrew.
HOMEBREW_NO_AUTO_UPDATE=1 # disable homebrew's automatic updates.
brew install cocoapods
# Install CocoaPods dependencies.
cd macos
pod deintegrate
pod update
cd ..
# Install Flutter dependencies.
flutter pub get
dart run build_runner build -d
# flutter build macos
flutter build macos --release