XCode Archive failed to read asset tags

Question & Answer Builds
1

Bitrise Build Issue Report template

Description of the issue

Upon upgrading to the XCode 11.0 stack, the archive error fails. Previously, the application could build on the XCode 10.3 stack and can successfully build locally on the XCode 11.0 stack. The error is:

[03:37:49] e[32;1m$ xcodebuild “-workspace” “EQUE.xcworkspace” “-scheme” “EQUE” “clean” “archive” “-archivePath” "/var/folders/6q/wgy6jtp12w5gzgm9lzcglpqw0000gn/T/__archive__396438790/EQUE.xcarchive"e[0m

User defaults from command line:
IDEArchivePathOverride = /var/folders/6q/wgy6jtp12w5gzgm9lzcglpqw0000gn/T/__archive__396438790/EQUE.xcarchive

note: Using new build system

** CLEAN SUCCEEDED **

note: Using new build system
note: Planning build
note: Constructing build description
2019-09-26 03:38:06.543 xcodebuild[2381:13232] Requested but did not find extension point with identifier Xcode.IBBuildSupport.AssetCatalog.AssetTagScanner
error: failed to read asset tags: unexpected error generating result tags (in target ‘EQUE’ from project ‘EQUE’)

Environment:

Where did the issue happen?

This is using the XCode 11.0 and XCode 11.1 stack

Which build Step causes the issue and which version of the step?

xcode-archive@2.6.0

Reproducibility

  • Does a “Rebuild” help? (You can trigger a rebuild from the Build’s page, by clicking the “Rebuild” button in the top right corner of a finished build) : NO
  • Does a rebuild without caches help? (You can remove the Cache:Pull and Cache:Push steps temporarily to not to use the cache, or you can delete all the caches on the Settings tab of the app. : NO
  • Does the issue happen sporadically, or every time? : Everytime
  • Does upgrading the build Step to the latest version help? : NO
  • When did the issue start? :
    XCode 11.0 stack upgrade

Local reproduction

Can it be reproduced on your own Mac/PC by following our local debug guide? Please follow at least the first section (“Testing with a full clean git clone”) to make sure to test the state of the code what bitrise.io will get when it does a git clone in the clean environment! If possible please note which sections you tried.

NO

Local reproduction: Linux / Android (docker based) stack builds

Can it be reproduced by running the build locally, after doing a new git clone of the repository into the /tmp directory and running the build from there with the Bitrise CLI ( Bitrise CLI )? If no, can it be reproduced with Docker (using the same docker images / environment we use on bitrise.io)? Related guide: Redirecting… .

NO

Build log

Please copy paste the build’s bitrise.io URL here (or if the issue happens somewhere else then the full logs), or if you can’t share the url / log here then send the url or full log through a private channel (e.g. email - Contact us ), with a link to the related Discuss issue.

1 Like
2

Also seeing the same issue, did you get any help on this @EQUE?

3

Same here, any updates? This is quite the blocker…

1 Like
4

Seeing this as well. It’s not consistent though… retry a few times and the build seems to work…

5

Hey @EQUE, @SimonMitchell @iridic and @Toke!

Sorry about the delay.

This error is almost definitely related to https://github.com/CocoaPods/CocoaPods/issues/8122 .

The initial workaround we’d suggest is providing a -UseModernBuildSystem=0 to the Additional options for xcodebuild call in the Debug section of the Xcode Archive step.

If this does not help, our suggestion would be to copy ${TARGET_BUILD_DIR}/${UNLOCALIZED_RESOURCES_FOLDER_PATH}/Assets.car to the input files of the [CP] Copy Pods Resource script after pod install or pod update . – based on other experiences shared in the thread linked above.

6

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.