bitrise-steplib/steps-xcode-archive

"Xcode archive & Export for ios" step failing with "no archive generated at: <path>/Runner.xcarchive"

ajejoseph22 opened this issue · 4 comments

ajejoseph22 commented

Troubleshooting

  • I've searched discuss.bitrise.io for possible solutions.
  • Which version of the step is effected? xcode-archive@4
  • Is the issue reproducible with the latest version? YES
  • Does the issue happen sporadically, or every time? EVERY TIME
  • Is the issue reproducible locally by following our local debug guide? YES

Issue description

I have a flutter app and am trying to integrate CI on Bitrise. The android apk gets generated but when it comes to the ios IPA, it fails in the "Xcode archive & Export for ios" step with no archive generated at: <path>/Runner.xcarchive and without any descriptive error message.

The contents of my xcodebuild-archive.log artifact file are as follows

Command line invocation:
    /Applications/Xcode-13.1.Release.Candidate.app/Contents/Developer/usr/bin/xcodebuild -workspace /Users/vagrant/git/ios/Runner.xcworkspace -scheme development -configuration Release-production -xcconfig /var/folders/g2/xnd8hpjs50v433gfrybz2nxh0000gn/T/366898388/temp.xcconfig clean archive -archivePath /var/folders/g2/xnd8hpjs50v433gfrybz2nxh0000gn/T/xcodeArchive937471011/Runner.xcarchive -destination generic/platform=iOS -resolvePackageDependencies

User defaults from command line:
    IDEArchivePathOverride = /var/folders/g2/xnd8hpjs50v433gfrybz2nxh0000gn/T/xcodeArchive937471011/Runner.xcarchive
    IDEPackageSupportUseBuiltinSCM = YES

Build settings from configuration file '/var/folders/g2/xnd8hpjs50v433gfrybz2nxh0000gn/T/366898388/temp.xcconfig':
    COMPILER_INDEX_STORE_ENABLE = NO

resolved source packages:

Bitrise info

Creating the Archive ...
[04:19:08] $ xcodebuild "-workspace" "/Users/vagrant/git/ios/Runner.xcworkspace" "-scheme" "development" "-configuration" "Debug-development" "-xcconfig" "/var/folders/4j/sw1y58511p32ql7smr4n5xwh0000gn/T/432646111/temp.xcconfig" "clean" "archive" "-archivePath" "/var/folders/4j/sw1y58511p32ql7smr4n5xwh0000gn/T/xcodeArchive438928818/Runner.xcarchive" "-destination" "generic/platform=iOS" "-resolvePackageDependencies"

Last lines of the Xcode's build log:

Command line invocation:

/Applications/Xcode.app/Contents/Developer/usr/bin/xcodebuild -workspace /Users/m/Documents/cbh/clipboard-facility-app/ios/Runner.xcworkspace -scheme development -configuration Debug-development -xcconfig /var/folders/4j/sw1y58511p32ql7smr4n5xwh0000gn/T/432646111/temp.xcconfig clean archive -archivePath /var/folders/4j/sw1y58511p32ql7smr4n5xwh0000gn/T/xcodeArchive438928818/Runner.xcarchive -destination generic/platform=iOS -resolvePackageDependencies


User defaults from command line:

IDEArchivePathOverride = /var/folders/4j/sw1y58511p32ql7smr4n5xwh0000gn/T/xcodeArchive438928818/Runner.xcarchive

IDEPackageSupportUseBuiltinSCM = YES


Build settings from configuration file '/var/folders/4j/sw1y58511p32ql7smr4n5xwh0000gn/T/432646111/temp.xcconfig':

COMPILER_INDEX_STORE_ENABLE = NO


resolved source packages:

You can find the last couple of lines of Xcode's build log above, but the full log will be also available in the raw-xcodebuild-output.log

The log file will be stored in $BITRISE_DEPLOY_DIR, and its full path will be available in the $BITRISE_XCODE_RAW_RESULT_TEXT_PATH environment variable.


Exporting outputs...

The xcodebuild archive log path is now available in the Environment Variable: BITRISE_XCODEBUILD_ARCHIVE_LOG_PATH (value: /var/folders/4j/sw1y58511p32ql7smr4n5xwh0000gn/T/deploy693254122/xcodebuild-archive.log)

no archive generated at: /var/folders/4j/sw1y58511p32ql7smr4n5xwh0000gn/T/xcodeArchive438928818/Runner.xcarchive
ajejoseph22 commented

Can anyone help please?

cc @ofalvai

bitrise-coresteps-bot commented

Hello there, I'm a bot. On behalf of the community I thank you for opening this issue.

To help our human contributors focus on the most relevant reports, I check up on old issues to see if they're still relevant.
This issue has had no activity for 90 days, so I marked it as stale.

The community would appreciate if you could check if the issue still persists. If it isn't, please close it.
If the issue persists, and you'd like to remove the stale label, you simply need to leave a comment. Your comment can be as simple as "still important to me".

If no comment left within 21 days, this issue will be closed.

ajejoseph22 commented

Forgot to update this. After further trials and errors, this issue was resolved by changing the apple authentication method from 'Apple ID' to 'API key'.