Xcode Cloud

RSS for tag

Automate workflows to test, analyze, build, and distribute your app, and integrate them with other developer tools, such as TestFlight and App Store Connect.

Xcode Cloud Documentation

Post

Replies

Boosts

Views

Activity

Xcode Cloud fatal: Device not configured
Hi Folks, We've been using Xcode Cloud for a year without any issues. Recently, our IT team switched authentication from LDAP to Azure SAML SSO. Since then, we've been getting the following error whenever Xcode Cloud launches a build: "Run command: '/bin/rm -rf /Volumes/workspace/repository &> /dev/null && GIT_TRACE2_PERF=/tmp/git_trace2_perf GIT_TRACE2_EVENT=/tmp/git_trace2_event git init /Volumes/workspace/repository && GIT_TRACE2_PERF=.....etc." "could not read Username for 'http://bitbucket.***': Device not configured Command exited with non-zero exit-code: 128" Any idea what we need to change to get things working again? Thank you Cam
1
0
49
7h
Can TestFlight be used to test build for Mac Sequoia
I have an app that I would like to test on Mac Sequoia. But when I build in Xcode Cloud, it seems to fail with a This bundle is invalid. Apple is not currently accepting applications built with this version of the OS. It also complains about the release train being closed, but I created a new release (set to manually be released). And it is pulling an old CFBundleShortVersionString somehow, but the other app versions (iOS and VisIonOS) in the same Xcode Cloud build work fine.
0
0
37
1d
Xcode Cloud SIGILL Crashes
This issue started to appear in the last couple of weeks. And it's annoying because Xcode Cloud actually is based on build duration. Here is a sample: The whole build took like 10 minutes. We can easily consume the 25 hours free tier because of these. The crash logs are completely useless. And the failing tests change from one run to the other and on different simulators. I really hope Xcode Cloud team look into this as it's frustrating and kills the whole point of Xcode Cloud (BTW, these issues won't happen on Bitrise).
5
0
137
1w
Can the NSPersistentCloudKitContainer mirror the data from the cloudKit public database to the local Core Data if the user is not logged in?
I'm currently syncing Core Data with the CloudKit public database using NSPersistentCloudKitContainer. The app starts with an empty Core Data store locally and at the app launch it downloads the data from CloudKit public database to the Core Data store, but this can only be accomplished if the user is logged in, if the user is not logged, no data gets downloaded and I get the error below. Can the NSPersistentCloudKitContainer mirror the data from the CloudKit public database to the local Core Data even if the user is not logged in? Can someone please confirm this is possible? The reason for my question is because I was under the impression that the users didn't need to be logged to read data from the public database in CloudKit but I'm not sure this applies to NSPersistentCloudKitContainer when mirroring data. I know I can fetch data directly with CloudKit APIs without the user beign logged but I need to understand if NSPersistentCloudKitContainer should in theory work without the user being logged. I hope someone from Apple sees this question since I have spent too much time researching without any luck. Error Error fetching user record ID: <CKError 0x600000cb1b00: "Not Authenticated" (9); "No iCloud account is configured"> CoreData: error: CoreData+CloudKit: -[NSCloudKitMirroringDelegate _performSetupRequest:]_block_invoke(1192): <NSCloudKitMirroringDelegate: 0x600003b00460>: Failed to set up CloudKit integration for store: <NSSQLCore: 0x10700f0d0> (URL: file:///Users/UserName/...
4
0
120
3d
Difficulties getting Xcode Cloud to automatically build when a commit is pushed
Hello! I'm having difficulties getting Xcode Cloud to see new changes to my files in my project that are being pushed. Previously, this was due to some network situation on my GitLab self-hosted server. This has likely been changed but I'm having difficulties because I tried to use an integration in GitLab for App Store Connect which isn't the same as Xcode Cloud and so as a result it didn't work. I tried starting over and setting up the system from scratch but the web hook hasn't appeared as it had done the first time I set it up. Does anyone know how to set up the web hook manually for Xcode Cloud so that Xcode Cloud is notified when a new push and other relevant events occur in my repository? The web hook that was previously there would error when I tried testing it on the GitLab end, but since I had deleted it, the web hook is not longer present and I was unable to recreate it as part of the setup procedure because it was pretty opaque to me the first time around and I followed the procedure in the documentation to get it to work. Xcode Cloud works fine when I manually start a build.
2
0
147
1w
XcodeCloud and VisionOS
I'm having issues compiling the visionOS app via XcodeCloud. Here's the error: 2024-06-20T09:24:47.634651911Z compileSkybox /Volumes/workspace/DerivedData/Build/Intermediates.noindex/ArchiveIntermediates/Fi22/InstallationBuildProductsLocation/Applications/VR22.app/ImageBasedLighting.rclink /Volumes/workspace/repository/Fi22/ImageBasedLighting.skybox (in target 'Fi22' from project 'Fi22') 2024-06-20T09:24:47.634669847Z cd /Volumes/workspace/repository 2024-06-20T09:24:47.634681756Z /Applications/Xcode.app/Contents/Developer/usr/bin/rctool create skybox -skyboxPath=/Volumes/workspace/repository/Fi22/ImageBasedLighting.skybox -o=/Volumes/workspace/DerivedData/Build/Intermediates.noindex/ArchiveIntermediates/Fi22/InstallationBuildProductsLocation/Applications/VR22.app 2024-06-20T09:24:47.634730433Z [91mError: [39m There is no available Metal device on this system. 2024-06-20T09:24:47.634745602Z Command compileSkybox failed with a nonzero exit code How do I configure XcodeCloud to use an instance with Metal support? Another option would be precompiling the skybox but I couldn't find any info on that either.
1
1
75
5d
Xcode Cloud Export archive for development distribution fails every time.
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
1
0
96
5d
Xcode cloud setup not working
I finally signed up for Xcode cloud, but it doesn't work after successful GitHub app installation. 401 in the console for: https://appstoreconnect.apple.com/olympus/v1/providerSwitchRequests I tried multiple things, even wrote to apple. Is it only for payed GitHub users? I have a free private repo. Hope someone has an idea. This is the error message when I give Xcode Cloud access to all repositories: Die Verbindung von Xcode Cloud mit deinem Quellcodeverwaltungsanbieter konnte nicht erstellt werden. Translation: The connection from Xcode Cloud to your source code management provider could not be established.
0
0
98
1w
Xcode Cloud builds successfully but fails deployment preparation for "TestFlight and App Store" with: Invalid Signature. Code failed to satisfy specified code requirement(s). The file at path “{App Name}.app/{App Name}” is not properly signed.
Xcode Cloud succeeds in building the Release configuration of the app, but whenever deployment preparation is set to "TestFlight and App Store" the last step fails with: ITMS-90035: Invalid Signature. Code failed to satisfy specified code requirement(s). The file at path “{AppName}.app/{AppName}” 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. When I build for release (with manual signing) everything works as expected and uploading to TestFlight for external testing works. I have tried to removed every imported framework, library, file etc. only keeping the bare minimum and still Xcode Cloud fails with the same error. I even created a new empty project but I still get the same error. My only guess is that something is off with the automatically generated certificates (or provisioning profiles) that Apple creates. Is there any way to figure out what specifically makes the signing fail? Is there a way to reset Xcode Cloud to clear all data and caches, revoke all certificates and remove all accosiated provisioning profiles?
8
1
1.1k
Feb ’24
Xcode Cloud stopped working: neither Xcode nor browser can connect
I started to use Xcode Cloud recently trying to understand how the whole build process etc. works. I created some workflows, integrated ci scripts to let fastlane create snapshots in the end, and everything seem to work while I was making progress step by step to get it up and running (struggling with the environment, etc.). Then last night it suddenly stopped working in the form, that Xcode shows the builds, but the last build still shows a spinner, although the job has finished already When I try to cancel the last run from Xcode (thought it was not finished) I get an error: Failed to Cancel Build 57. An internal error occurred while authenticating. Try again later. (FB13802231) When I open Manage Workflows…, Xcode suddenly shows "This operation could not be completed" and details reveal: The operation couldn’t be completed. ((extension in XcodeCloudKit):XcodeCloudAPI.Client.HTTPClientError error 0.) (FB13802952) Trying to access the Xcode Cloud tab of the app or general from users and permissions shows a white page with a spinner. The console filtered by Xcode shows (around the time the error happens): Failed to query public key: 0xe800000c The Safari browser console shows: An internal error occurred while authenticating. Try again later. What works: I can login to AppStore Connect without problem. I am logged-in in Xcode (but there's no option to logout and re-login) I can use tools like fastlane with API calls (or some xcc command line tool) and list the products, workflows and runs using my API key. From this information I also figured out, that the build in question (57) where Xcode still shows the spinner, has finished (failing) already. I was also able to start a new build manually (58) via API, which however has finished 3 seconds after creation, but has never started (startedDate is empty while createdDate and finshedDate contains data). I was able to delete the workflow via API in hope that the problem goes away, but theres no change in Xcode (still shows the same picture with the workflow and last build 57 spinning). I should have used <4 / 25 hours of free plan of Xcode Cloud this month, so limit not exceeded. I'm on macOS 14.4.1, Xcode 15.3. Seems I can't make use of Xcode Cloud at all anymore right now which keeps me from proceeding now on my way to first time deliver to AppStore (still understanding and learning). I also provided info about the 2 Xcode errors as feedback, which I linked above. Any help on how to reset / do whatever is necessary to make it work again is very much appreciated.
1
0
296
May ’24
Xcode Cloud Archive - visionOS fails with Info.plist errors?
Today I have tried to add a second archive action for visionOS. I had added a visionOS destination to my app target a while back and can build and archive my app for visionOS in Xcode 15.3 locally, and also run it on the device. Xcode Cloud is giving me the following errors in the Archive - visionOS action (Archive - iOS works): Invalid Info.plist value. The value for the key 'DTPlatformName' in bundle MyApp.app is invalid. Invalid sdk value. The value provided for the sdk portion of LC_BUILD_VERSION in MyApp.app/MyApp is 17.4 which is greater than the maximum allowed value of 1.2. This bundle is invalid. The value provided for the key MinimumOSVersion '17.0' is not acceptable. Type Mismatch. The value for the Info.plist key CFBundleIcons.CFBundlePrimaryIcon is not of the required type for that key. See the Information Property List Key Reference at https://developer.apple.com/library/ios/documentation/general/Reference/InfoPlistKeyReference/Introduction/Introduction.html#//apple_ref/doc/uid/TP40009248-SW1 All 4 errors are annotated with "Prepare Build for App Store Connect" and I get them for both "TestFlight (Internal Testing Only)" and "TestFlight and App Store" deployment preparation options. I have tried to remove the visionOS destination and add it back, but this is not changing the project at all. Any ideas what I am missing?
4
2
516
Apr ’24
PrivacyInfo.xcprivacy: No such file or directory
I've been running into problems when building on Xcode cloud. I keep getting errors with regards to PrivacyInfo.xcprivacy: No such file or directory. I'm not sure what the next steps are, as I originally built with only three errors: Then I attempted to pod install and pod update, and even tried to alter the target membership, but that only had me get more errors: I've looked at some of the other questions and responses in the forum about this issue, but none of them seemed to fix the No such file or directory issue. Any advice would be appreciated. Thanks!
1
0
1k
Mar ’24
Xcode Cloud build phase has massively slowed down
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
12
12
820
3w