@rogerluan @autimio-brito-gaivota thanks for your valuable input guys! I am finally able to build with fastlane and circle ci for all the following xcode versions:

• 11.7.0
• 12.0.1
• 12.2.0
• 12.4.0

I tried all these 3 that previously were failing. It was fairly easy with @rogerluan instructions; Essentially and after reading the links mentioned I did the following:

In Podfile:

1. Added this snippet on top and below line target 'project name' do:

pre_install do |installer|
    $RNMBGL.pre_install(installer)
end

1. Changed pod install line for ‘react-native-mapbox-gl’ installation to:

pod 'react-native-mapbox-gl', :git => 'https://github.com/react-native-mapbox-gl/maps.git', :branch => 'master'

1. Added this snippet on bottom and inside the post_install:

$RNMBGL.post_install(installer)
installer.pods_project.targets.each do |target|

1. Specified the needed xcode binary version in circle ci config.yml file

If someone else can verify this I’d say we can close this issue, cheers 🎉

Hello everybody!

I finally managed to solve the problem here, after two weeks of doing several tests. But I don’t know if it will be the same solution for you.

What made it work here was the following:

1. I compared the podfile.lock with the last branch that the build had worked. I verified that some libraries were with a different version with the branch that was with problem. With that, I adjusted podfile.lock with the versions that worked before (I believe the file had been deleted before, and that’s why those versions have been updated, possibly breaking something). What I had different was the libraries:

   • @react-native-mapbox-gl-mapbox-static (from 5.9.0 I changed to 5.8.0)
   • CocoaAsyncSocket (from 7.6.5 I changed to 7.6.4)
   • Flipper-Folly (from 2.5.1 to 2.2.0)

.: To check this in an easier way, I used the tool https://editor.mergely.com/

1. I have added this to my Podfile: use_flipper!({'Flipper-Folly' => '2.2.0'})

2. I deleted the Cocoapods cache rm -rf ~/Library/Caches/CocoaPods

3. I deleted the Pods folder (inside the ios folder) rm -rf Pods

4. I reinstalled the Pods pod install (inside the iOS folder) or npx pod-install (project root)

.: You may notice that this will adjust your project.pbxproj.

After following these steps, everything worked out here as it was before!

Xcode Version 12.4 (12D4e)

Hope this can help someone S2

@marudy we had the same issue and in our case it was because one of our libraries (mapbox) had issues with cocoapods 1.10.1. After we downgraded the installed pods version to 1.9.3, we finally were able to build.

@nodediggity just updated my original comment with the extra certificates command and how we have configured it inside the fastfile. Looks like an issue hard to pass around it at the moment. Have tried quite a few things like cleaning the build, using xcode_select explicitly, resolving package dependencies of swift package manager explicitly but nothing has worked out.

I think if you have tried workarounds it worths mentioning them along with your provided logs. Cheers man

Hey all,

Apologies for being MIA for so long. So I took some time to investigate this issue and although I couldn’t test this issue myself (yes, I did dig into this rabbit hole of trying to install this react native thing 😭😂), I did find some answers, which I’m hoping will do the trick for you guys:

There were strong indicators that this issue was related to some type of React Native Maps library, as seen here and here (both are comments in this page). So then I dug into what that lib was, and ended up finding this issue: https://github.com/react-native-mapbox-gl/maps/issues/1097 Looks like that issue describes what you guys are seeing as well, except the user is not building via fastlane, he’s archiving and exporting manually via Xcode UI. Has anyone here tried that to see if the issue is exclusive to fastlane?

With that issue in hand, looks like this guy found a workaround 29 days ago, and then this other guy opened a Pull Request to fix the issue 16 days ago, which already got merged, but has not yet been released. Note that the fix requires changes to your Podfile regardless, see the PR description above.

Now, looks like you “just” have to consume the latest version of that pod available in master, and not the latest tag release. Stack Overflow shows how to point a pod to a specific branch.

Moreover, if you’re still facing issues, check the comments on the aforementioned PR ☝️ it mentions things related to the use_flipper!({ 'Flipper-Folly' => '2.3.0' }) as @autimio-brito-gaivota mentioned above as well. Ref.: https://github.com/react-native-mapbox-gl/maps/pull/1262#issuecomment-791588054

Note that @autimio-brito-gaivota was able to get his environment fixed (described here) by downgrading that dependency to an earlier version. That might work for some as well. But some others mentioned that that wasn’t a viable alternative for them.

I hope this helps everyone. Let me know by commenting below if this worked out for you guys. If it still won’t work, try to export manually via Xcode to see if it works, please 🙏

@autimio-brito-gaivota thanks for your help man, but hard-pinning versions of my libraries is not a viable solution for me.

This is something that needs to be addressed internally from fastlane team. I really hope the guys will manage to find the time and prioritize this. @max-ott @rogerluan kindly follow up on this or let us know what is a viable way of providing an “extraction” of our pipeline ?

Thanks

@autimio-brito-gaivota Thank you very much for spending your time looking into this. I will follow your instructions on my project very soon and report back to you the results.

@NathanJozef failed for me with xcode 11.7 as well. Renamed the title to a more proper one. Thanks for your input.

I am running into the same issue here. My CircleCI instance and my own machine are both failing with this error. Am also using match and trying to sign with an adhoc profile.

I’ve followed through the conversation here. While I don’t have much to offer by way of solution at the moment I can confirm that the archived app does have a plist in the app package. Nothing in the containing archive package. What I can confirm is that building an archive from Xcode with the same profile produces a successful build.

The CircleCI instance was failing using Xcode 11.7 too. Unless it is a coincidence, this issue isn’t exclusive to Xcode 12 in all circumstances.

[01:07:50]: ▸ Archive Succeeded
[01:07:50]: Generated plist file with the following values:
[01:07:50]: ▸ -----------------------------------------
[01:07:50]: ▸ {
[01:07:50]: ▸   "compileBitcode": false,
[01:07:50]: ▸   "uploadBitcode": false,
[01:07:50]: ▸   "provisioningProfiles": {
[01:07:50]: ▸     "com.livingmap.surveyapp": "match AdHoc com.livingmap.surveyapp"
[01:07:50]: ▸   },
[01:07:50]: ▸   "method": "ad-hoc",
[01:07:50]: ▸   "signingStyle": "manual"
[01:07:50]: ▸ }
[01:07:50]: ▸ -----------------------------------------
[01:07:50]: $ /usr/bin/xcrun /Users/nathanziabek/.rbenv/versions/2.7.1/lib/ruby/gems/2.7.0/gems/fastlane-2.175.0/gym/lib/assets/wrap_xcodebuild/xcbuild-safe.sh -exportArchive -exportOptionsPlist '/var/folders/9j/qyc2bgl52v31yy774p58709m0000gn/T/gym_config20210224-15892-1wd75cg.plist' -archivePath /Users/nathanziabek/Library/Developer/Xcode/Archives/2021-02-24/LMSurveyApp\ 2021-02-24\ 01.04.17.xcarchive -exportPath '/var/folders/9j/qyc2bgl52v31yy774p58709m0000gn/T/gym_output20210224-15892-akyjho'
rbenv detected, removing env variables
rbenv: shell integration not enabled. Run `rbenv init' for instructions.
+ xcodebuild -exportArchive -exportOptionsPlist /var/folders/9j/qyc2bgl52v31yy774p58709m0000gn/T/gym_config20210224-15892-1wd75cg.plist -archivePath '/Users/nathanziabek/Library/Developer/Xcode/Archives/2021-02-24/LMSurveyApp 2021-02-24 01.04.17.xcarchive' -exportPath /var/folders/9j/qyc2bgl52v31yy774p58709m0000gn/T/gym_output20210224-15892-akyjho
error: archive at path '/Users/nathanziabek/Library/Developer/Xcode/Archives/2021-02-24/LMSurveyApp 2021-02-24 01.04.17.xcarchive' is malformed
** EXPORT FAILED **
[01:07:51]: Exit status: 65

Captured Output

Command Used: ios alpha --verbose --capture_output

DEBUG [2021-02-24 01:28:40.88]: Checking if there are any plugins that should be loaded...
DEBUG [2021-02-24 01:28:40.88]: Loading 'fastlane-plugin-firebase_app_distribution' plugin
INFO [2021-02-24 01:28:40.88]: gem 'fastlane-plugin-firebase_app_distribution' is already installed

default_platform(:ios)

platform :ios do
  
  before_all do
  end

  desc "Alpha Build"
  lane :alpha do |options|
    #match(type: "development", readonly: true)
    # create_keychain(
    #   name: ENV["MATCH_KEYCHAIN_NAME"],
    #   password: ENV["MATCH_PASSWORD"],
    #   default_keychain: true,
    #   unlock: true,
    #   timeout: 3600,
    #   add_to_search_list: true
    # )
    match(
      type: "adhoc",
      keychain_name: ENV["MATCH_KEYCHAIN_NAME"],
      keychain_password: ENV["MATCH_PASSWORD"],
      readonly: true
    )
    cocoapods(clean_install: true)
    gym(
      scheme: "<Redacted>",
      export_method: "ad-hoc",
      include_bitcode: false,
      export_options: {
        compileBitcode: false,
        uploadBitcode: false,
        provisioningProfiles: {
          "<Redacted>" => "match AdHoc <Redacted>"
        }
      },
      silent: false,
      suppress_xcode_output: false,
      output_directory: 'output',
      output_name: "<Redacted>"
    )
    firebase_app_distribution(
      app: ENV["FIREBASE_APP_ID"],
      #testers: “TESTER-EMAILS”,
      groups: “internal”,
      release_notes: “Currently Testing”,
      firebase_cli_path: “/usr/local/bin/firebase”,
      ipa_path: “output/<Redacted>”
    )
    slack_success
  end
  
  lane :slack_success do
    commit = last_git_commit()
    slack(
      use_webhook_configured_username_and_icon: true,
      pretext: "* iOS Build #" + ENV['CIRCLE_BUILD_NUM'] + " Succeeded!* :man-surfing:",
      message: "iOS <Redacted> successfully uploaded to Firebase..",
      default_payloads: [:git_branch],
      attachment_properties: {
        color: "good",
        fields: [
          {
            title: "Commit Message",
            value: commit[:message]
          },
        ],
        actions: [
          {
            type: "button",
            text: "View CircleCI Job #" + ENV['CIRCLE_BUILD_NUM'],
            url: ENV['CIRCLE_BUILD_URL'],
            style: "default"
          },
          {
            type: "button",
            text: "Install Build",
            url: "itms-services://0.0.0.0?action=download-manifest&url=" + "https://circleci.com/api/v1.1/project/github/livingmap/mobile-survey-app/" + ENV['CIRCLE_BUILD_NUM'] + "/artifacts/0/~/mobile-survey-app/ios/output/manifest.plist?circle-token=" + ENV['CIRCLE_TOKEN'] + "&branch=" + git_branch(),
            style: "primary"
          },
        ]
      },
    )
  end

  after_all do |lane|
  end

  error do |lane, exception|
    commit = last_git_commit()
    slack(
      use_webhook_configured_username_and_icon: true,
      pretext: "* iOS Build #" + ENV['CIRCLE_BRANCH'] + " Failed!* :cry:",
      message: "Something went wrong with the build. Check the build system output.",
      default_payloads: [:git_branch, :last_git_commit_message],
      attachment_properties: {
        color: "danger",
        fields: [
          {
            title: "Commit Message",
            value: commit[:message]
          },
        ],
        actions: [
          {
            type: "button",
            text: "View CircleCI Job #" + ENV['CIRCLE_BUILD_NUM'],
            url: ENV["CIRCLE_BUILD_URL"],
            style: "warning"
          },
        ]
      },
      success: false,
    )
  end
end

# app_identifier("[[APP_IDENTIFIER]]") # The bundle identifier of your app
# apple_id("[[APPLE_ID]]") # Your Apple email address


# For more information about the Appfile, see:
#     https://docs.fastlane.tools/advanced/#appfile

I can confirm i’m getting the same error while trying to build with xcode 11.7 as well.

@rogerluan I have a huge project along with a huge pipeline on the circle ci. Can you propose a way to “extract” somehow the functionality you need if there is one? Thanks

@nodediggity thanks commenting. yes I’m using match as well and manual signing style. The error above is happening for the match AdHoc use case. As this one is keep failing i have not moved on to the match AppStore one yet