fastlane: ARCHIVE FAILED: Exit status: 65, Gym failed

This solved my problem: https://stackoverflow.com/questions/73765469/signing-for-googlesignin-googlesignin-requires-a-development-team.

I’m having the exactly same issue building with Github Actions. same as https://github.com/fastlane/fastlane/issues/20276

I’m able to build with my Mac (M1) just fine.

There hasn’t been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest fastlane version and check if that solves the issue. Let us know if that works for you by adding a comment 👍

Friendly reminder: contributions are always welcome! Check out CONTRIBUTING.md for more information on how to help with fastlane and feel free to tackle this issue yourself 💪

This issue will be auto-closed if there is no reply within 1 month.

When using match + gym on Fastlane. Using update_code_signing_settings before match ins what did the trick, the resulting operations look like this:

update_code_signing_settings(
    use_automatic_signing: false,
    team_id: team_id,
    targets: [target],
    code_sign_identity: "*****",
    profile_name: "your_profile_name",
    path: PROJECT_PATH
  )

  match(
    username: options[:username],
    git_url: certificates_url,
    app_identifier: app_identifier,
    type: "appstore", 
    team_id: team_id
  )
  
  gym(
    project: PROJECT_PATH,
    export_method: "app-store",
    configuration: "Release", 
    scheme: scheme,
  )

I had the exact same problem and finally found out that the cause of this error because i haven’t put my .env file onto my root project. I had pre-action script to read the env file as i am using react-native-config for different schemes, that’s why i’m getting error if i dont have the .env file. So my solution is to put base64 string of the env file to github secret and then copy & decode it in the github workflow. After that everything works like a charm. Maybe this can help someone 😃

I had an exit code 65 looking over my logs I found I had a custom script that was copying a env file. For some reason that started causing a build error in the new xCode. I deleted that script by editing the scheme config.

Unsure this will be related to your issue but might be a cause for someone in the future.

I received this issue after upgrading to xcode 14. First answer solved it for me: https://stackoverflow.com/questions/74275390/fastlane-with-xcode-14-archive-failed

Had this problem, struggled for days to solve it. Putting my solution here too for posterity:

I’m using Flutter, but I think this applies globally. If you introduce a new iOS build target into your app, and that target required you to add a new identifier, your fastlane instance probably needs a 2nd mobile provision referenced.

For example, my original project referenced com.company.project, but then I added a target that used com.company.project.Broadcast-Extension. My fastlane builds started failing with Exit Status 65, but XCode was still able to build it.

Check https://developer.apple.com/account/resources/identifiers/list to see if a new identifier got added to your project. For me, I had created a Broadcast Extension to enable screen-share on LiveKit.io. As part of the process, I had to create a new Upload Broadcast Extension target in my XCode project. I did so without updating fastlane with a second mobile provision, and my builds began failing.

The solution was to create a second provisioning profile for my broadcast extension at https://developer.apple.com/account/resources/profiles/list with the new identifier. Then, install both my provisioning profiles with:

install_provisioning_profile(path: <insert_path_to_mobile_provision>)

Finally, create an ExportOptions.plist file based off this template which specifies what mobile provisioning profile should be used for each target. Ensure each name/identifier pair EXACTLY matches your provisioning profile as seen in at https://developer.apple.com/account/resources/profiles/list and identifier as seen in https://developer.apple.com/account/resources/identifiers/list. Reference the ExportOptions.plist file by passing its path to

build_app(
      [...]
      export_options: <Path to ExportOptions.plist>,
    )

For CI/CD, I recommend using https://github.com/yukiarrr/ios-build-action which massively simplifies the iOS build process headache.

I hope this helps fellow engineers!

I was having this issue on GitHub actions while trying to run fastlane with match to deploy iOS app to TestFlight, what fixed for me was disable_automatic_code_signing before calling match.

   disable_automatic_code_signing(
    team_id: "",
    profile_name: "",
    code_sign_identity: ''
  )

It just means that command that was being run in PhaseScriptExecution wasn’t successful, you have to check detailed logs from the execution. The location of the log is probably mentioned somewhere in the fastlane output.

in my case it was a react-native issue https://github.com/react-native-community/upgrade-support/issues/138

okay, let me directly use xcodebuild command. No i didn’t try with previous fastlane version. i’ll try and let you know.