Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Xcode 14: Could not find transporter error #20664

Closed
4 tasks done
mzsanford opened this issue Sep 16, 2022 · 8 comments
Closed
4 tasks done

Xcode 14: Could not find transporter error #20664

mzsanford opened this issue Sep 16, 2022 · 8 comments

Comments

@mzsanford
Copy link

New Issue Checklist

Issue Description

After switching to Xcode 14 the fastlane beta command I had been using, which calls upload_to_testflight, began to fail with the error [!] Could not find transporter at /Applications/Xcode.app/Contents/Developer/. Please make sure you set the correct path to your Xcode installation.

Command executed

The call in question boils down to:

    upload_to_testflight(
      apple_id: team_id,
      changelog: test_notes
    )

I'm not at liberty to post the full code and output because it includes content from the codebase I am contracted not to disclose. I checked the installation in question and Xcode 14 does not have the itms program that Fastlane is looking for. Perhaps it has been renamed or replaced.

@fastlane-bot
Copy link

It seems like you have not included the output of fastlane env
To make it easier for us help you resolve this issue, please update the issue to include the output of fastlane env 👍

@freddi-kit
Copy link
Contributor

This problem is fixed 2.210.0 version. Can you see your fastlane version by --version?

@mzsanford
Copy link
Author

Turns out I had updated when I started investigating the issue and 2.210.0 was released after that. I upgraded and confirmed it fixed the issue.

@LugonjaAleksandar
Copy link

Did anyone figure out how to setup specific version (2.210.0) on github actions? There is no option provided for it, and the error persists for maierj/fastlane-action@v2.3.0

@SarjuHansaliya
Copy link

SarjuHansaliya commented Oct 28, 2022

Did anyone figure out how to setup specific version (2.210.0) on github actions? There is no option provided for it, and the error persists for maierj/fastlane-action@v2.3.0

You will need to update Gemfile.lock file with the version you want so github action can take version from there.
You can use bundle update fastlane to update fastlane version in Gemfile.lock

@LugonjaAleksandar
Copy link

Did anyone figure out how to setup specific version (2.210.0) on github actions? There is no option provided for it, and the error persists for maierj/fastlane-action@v2.3.0

You will need to update Gemfile.lock file with the version you want so github action can take version from there. You can use bundle update fastlane to update fastlane version in Gemfile.lock

Yes, that was the issue for me. Once I've added lock file to gitignore, it started using latest version and all worked fine.

@piotrsmajek
Copy link

Is there any workaround for it? We can't update fastlane from 2.200.0 version due to this issue lyndsey-ferguson/fastlane-plugin-test_center#384

@walkingbrad
Copy link

I found that this error still comes up (on v2.211.0) when we pass verify_only: true, at least in my one test of doing so. Setting it to false allows the action to succeed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants