Hi,
I am using Xcode Cloud to build our app, and our app has the cocoapods dependency NMapsMap(Korean map library from Naver inc.).
https://navermaps.github.io/ios-map-sdk/guide-en/
The library uses git-lfs to download its data for the map, however it keeps failing and retrying 3 times to download with this error(and finally fails)
Showing All Messages
[!] Error installing NMapsGeometry
[!] /usr/bin/curl -f -L -o /Volumes/workspace/tmp/d20240826-7482-5cn94o/file.zip https://repository.map.naver.com/archive/pod/NMapsGeometry/1.0.2/NMapsGeometry.zip --create-dirs --netrc-optional --retry 2 -A 'CocoaPods/1.15.2 cocoapods-downloader/2.1'
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0curl: (6) Could not resolve host: repository.map.naver.com
Warning: Problem : timeout. Will retry in 1 seconds. 2 retries left.
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0curl: (6) Could not resolve host: repository.map.naver.com
Warning: Problem : timeout. Will retry in 2 seconds. 1 retries left.
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0curl: (6) Could not resolve host: repository.map.naver.com
My ci_post_clone.sh file is here, and doesn't seem to have something to be wrong.
export HOMEBREW_NO_INSTALL_CLEANUP=1
brew install cocoapods
pod install
The issue could be DNS server issue between Apple Xcode Cloud servers and Naver repositories server, so I also posted to the Naver cloud forum.
Please help for this issue, and hope the build can resolve the host soon. Nowadays I manually build and distribute the codes in manual...
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
When I click "Register," this error appears. How can I allow Xcode Cloud to access a self-managed GitLab? Do I need to configure the GitLab server?
For the last hour or so, builds to TestFlight from our Xcode Cloud workflow are sitting in the "TestFlight Internal Testing - iOS" step with no log messages... Normally this step is pretty quick, but it's as if something is hanging there. This seems to affect multiple branches (we use GitHub).
Is something hosed on the TestFlight side/anyone else experiencing this?
Edit ah shortly after I posted this it finished :face-palm:. Perhaps this was related to the Xcode Cloud outage earlier
Since we integrated xcode cloud into our project, workflows fail randomly when resolving dependencies from cocoapods (specifically when fetching the repo from github). The error is a 502 so seems like server side, and if we rebuild is usually goes away but we have to be constantly rebuilding failing workflows, loosing minutes and dev time instead of having it automated as we wanted. Any ideas?
Having an issue today where archives on Xcode Cloud are failing at the Code Signing step. The error reported by Xcode Cloud has been one of the 2 following:
502 error from developerservices2.apple.com
Unexpected character 'u' (I assume this is in some way related to the HTTP failure above, but please correct me if I'm wrong)
Sometimes they even appear together, with the HTTP error as a warning and the unexpected character as the error
I assume this is some kind of Xcode Cloud / developer tools outage. I saw another post on the forum from 3 weeks ago that reported the same errors coming from Xcode Cloud. I also saw that there is a "Resolved Outage" with Xcode Cloud from 8/19 (maybe that is related)?
Has anyone found a way around this? Any updates on when this will be resolved? It has been happening for us consistently since the first Xcode Cloud archive that we ran today (around 10AM EDT).
I am part of a personal team where I have admin credentials. The account holder created a workflow when initializing Xcode Cloud but I can't see it in my App Store Connect. So I tried to create another workflow but when I do, I get the error "User does not exist". This is very annoying for us.
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]
I am using Xcode Cloud to build my Mac Catalyst app for Developer ID Distribution as a DMG package that must be codesigned and notarized. I have a ci_post_xcodebuild.sh script that runs after the Archive action.
This needs to perform the following tasks:
Produce a DMG from the provided exported archive located at CI_DEVELOPER_ID_SIGNED_APP_PATH
Codesign that DMG using the same certificate identity that Xcode Cloud used when automatic code signing the exported archive using cloud signing.
Notarize that code signed dmg with the notary service
Generate a Sparkle appcast.xml file
Upload the DMG and appcast.xml file to s3
The issue I am having is that I do not have access to the cloud signing keychain identity that Xcode Cloud uses to automatically codesign the exported archive.
I check for identities and none are found. Running:
security find-identity -v -p codesigning
There are no code signing identities available. Make sure you have a "Developer ID (Application)" certificate (with the private key) installed on your Mac with Keychain Access.
How can I access the cloud signing identity in this script so I can sign my DMG file before notarizing it?
I am currently experimenting with installing my own certificate in the build server keychain and run my own archive + export commands after the Build action completes. This is not ideal.
Thanks,
Andrew
I have registered a webhook URL but for every event triggered, my webhook URL does not receive any POST request.
In my App Store Connect Xcode Cloud > Webhook Setting, I can see all the webhook failed to send, they all returned `Unexpected response code for CONNECT: 403
`
I tried testing my webhook URL from Postman, it works fine, but not from Xcode Cloud Webhook.
Hi all,
I have a UI Automation Test suite with a large number of test cases, that typically takes me 7 hours to run. When I setup the workflow on XCode cloud, I received the following 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."
Is there any way to extend the build time?
What is a build? I have two actions in my workflow. Build Action (that took 3 minutes) and the test step that took 2 hour 4 minutes. Am not clear how the 120 minute window is calculated.
My app requires NodeJS to build (a Cordova app). Can I even use XCode Cloud to build it? Can I run Docker containers, or can I install NodeJS via a prebuild script?
(BTW I'm only looking into this service as alternative to my existing Gitlab-CI + fastlane because I have been unable to automate my iOS app build due to all the signing/provisioning BS that apple requires! )
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/***.xcodeproj -scheme '***' -derivedDataPath /Volumes/workspace/DerivedData -hideShellScriptEnvironment
Error
Command exited with non-zero exit-code: 134
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
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.
Hi,
I am trying to setup a workflow for my project and I am not able to get to the "Grant Access" step. After I click "Next" on the workflow, I see a "Grant Access to Your Source Code" window with "Loading source code repositories" message and a loading spinner. I see an error "This operation could not be completed". Clicking OK will just show me the previous Loading message.
My XCode is configured with our GitHub account. The lack of any error or steps for resolution is not helping. How do I proceed?
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 ?
I'm waiting over 1 hour 20 minutes to start build task
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.