Xcodecloud Xcodebuild Failed With Exit Code 70

Question

Created Oct ’24

Replies 6

Boosts 1

Participants 5

I'm running on xcode 16, the project archives just fine on the local machine. However, with xcodecloud. It's running into exist code 70 on the following command

xcodebuild -exportArchive -archivePath .....

#output


Showing All Errors Only

Build Archive

Export archive for ad-hoc distribution
Command exited with non-zero exit-code: 70

Command exited with non-zero exit-code: 70

Export archive for development distribution
Command exited with non-zero exit-code: 70

Command exited with non-zero exit-code: 70

Export archive for app-store distribution
Command exited with non-zero exit-code: 70

Command exited with non-zero exit-code: 70

Answered by John-Doe in 808720022

Turns out, I added an share extension with a new bundle id. The new id needs manually registered :|

The xcode cloud error might or may not be related to solving my error code 70. The export and distribute is the way to debug.

Boost

Answer 1

jhokit OP

Oct ’24

I'm also seeing random failures today at the very end of builds, when exporting the archive. Seems like after yesterday's outage, things aren't quite right yet.

0

Answer 2

jhokit OP

Oct ’24

@John-Doe Cloud builds and archiving are working for me now, after some random failures this morning. Hope it's cleared up for you.

0

Answer 3

John-Doe OP

Oct ’24

Accepted Answer

Turns out, I added an share extension with a new bundle id. The new id needs manually registered :|

The xcode cloud error might or may not be related to solving my error code 70. The export and distribute is the way to debug.

0

Answer 4

DTS Engineer OP

Apple

Oct ’24

I added an share extension with a new bundle id. The new id needs manually registered :|

From Xcode Cloud Release Notes

Some bundle IDs aren’t automatically registered when onboarding to Xcode Cloud. Workaround: In Xcode, Archive and Export your app for the App Store or manually register your bundle IDs in Certificates, Identifiers & Profiles.

0

Answer 5

brucezjt OP

Oct ’24

same question

Export archive for ad-hoc distribution Command exited with non-zero exit-code: 70

Export archive for development distribution Command exited with non-zero exit-code: 70

but app-store distribution successfully Export archive for app-store distribution Command executed successfully

bundle IDs no problem，Did someone fix it？

0

Answer 6

appleaday OP

4w

This is/was driving me nuts... after cleaning virtually all warnings, deleting identifiers, toggling automatic provisioning in Xcode and a million other things, the advice above may have been the key. Here is what I did:

From Xcode, perform an Archive of the iPhone app (I have the main app, widgets, and a companion watch app with its own widget extension as well (probably source of the problem)).

After the Archive is created, perform a Validate. After Validate, perform a Distribute, choose Custom, choose Release Testing, choose App Thinning "All". After this, it appears to be working again... I got a TestFlight notification on my phone. Fingers crossed for Xcode cloud build, next.

Update: Xcode Cloud did NOT work. I thought the above might reinitialize something but apparently not. Still failing on my watchOS archive:

Showing All Messages Run command: 'xcodebuild -exportArchive -archivePath /Volumes/workspace/tmp/0ad1cd3c-4b88-48c6-b61f-ace8da289cdd.xcarchive -exportPath /Volumes/workspace/adhocexport -exportOptionsPlist /Volumes/workspace/ci/ad-hoc-exportoptions.plist '-DVTPortalRequest.Endpoint=http://172.16.55.65:8089' -DVTProvisioningIsManaged=YES -IDEDistributionLogDirectory=/Volumes/workspace/tmp/ad-hoc-export-archive-logs -DVTSkipCertificateValidityCheck=YES -DVTServicesLogLevel=3'

New ideas welcome!

0