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
match "undefined method get_profiles" error with fastlane 2.218.0 #21762
Comments
+1 |
Not a solution, but a workaround for now: In your Gemfile, add the following line: (Make sure to remove it when this issue is fixed - not great to be locked to a specific version here.) |
Is it possible to "ignore" specific versions in the gem file? This would be much better than to lock one since the latter required additional action while ignoring specific versions can stay and is even a great documentation. |
You're right - there is. TIL!
EDIT: As pointed out below, there's no guarantee that the next version will fix the issue. It's probably safer to stick with the first workaround above. |
Wow did not know this!!! Is it also possible to specify multiple ones? |
@stherold Except that there is no guarantee that it will be fixed in the next version, so that's also not ideal. |
Yep, good point. I'll leave both options up above - do what you feel is best for your situation. |
I think something like this would work if you need to exclude multiple versions: |
Any idea how to force to install specific version of fastlane on Bitrise.io? ERROR: While executing gem ... (Gem::DependencyRemovalException)
Uninstallation aborted due to dependent gem(s)
/Users/vagrant/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/uninstaller.rb:155:in `uninstall_gem'
/Users/vagrant/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/uninstaller.rb:235:in `block in remove_all'
/Users/vagrant/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/uninstaller.rb:235:in `each'
/Users/vagrant/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/uninstaller.rb:235:in `remove_all'
/Users/vagrant/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/uninstaller.rb:126:in `uninstall'
/Users/vagrant/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/commands/uninstall_command.rb:198:in `uninstall'
/Users/vagrant/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/commands/uninstall_command.rb:184:in `uninstall_gem'
/Users/vagrant/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/commands/uninstall_command.rb:178:in `block in uninstall_specific'
/Users/vagrant/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/commands/uninstall_command.rb:170:in `each'
/Users/vagrant/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/commands/uninstall_command.rb:170:in `uninstall_specific'
/Users/vagrant/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/commands/uninstall_command.rb:132:in `execute'
/Users/vagrant/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/command.rb:327:in `invoke_with_build_args'
/Users/vagrant/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/command_manager.rb:252:in `invoke_command'
/Users/vagrant/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/command_manager.rb:192:in `process_args'
/Users/vagrant/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/command_manager.rb:150:in `run'
/Users/vagrant/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/gem_runner.rb:51:in `run'
/Users/vagrant/.asdf/installs/ruby/3.2/bin/gem:10:in `<main>'
ERROR: While executing gem ... (NoMethodError)
undefined method `request' for nil:NilClass
[@failed_dep.dependency, @activated.request.dependency]
^^^^^^^^ I can't run my workflows because we are using fastlane match :/ |
Try modifying
|
@lukasz-szyszkowski enter step fastlane in bitrise and set to false "update fastlane before running lane" - with this flag fastlane version locked in gemfile has no effect |
If you use Bundler to instal your gems, you can add something like this to your gemfile
Note that this is a temporary measure until the issue has been fixed |
Hi guys, thanks for reporting, and sorry for the breaking. I'm looking into this issue right now. UPD: Looks like the problem with readonly: true mode. |
This comment was marked as duplicate.
This comment was marked as duplicate.
The issue with match/sync_code_signing should be fixed in [match] fix cache issues in read-only mode. Would appreciate it if someone could confirm it works for them. |
changed it to false and works for me |
@nekrich I tested it with your change (by using |
Would this fix also address an issue when creating a cert:
[19:27:11]: Successfully generated .... which was imported to the local machine. Previous fastlane 2.217.0 & 2.216.0 work as expected with the same command. |
@scott-hill-alkami You can give it a try and see if it fixes the issue (see my comment above on how to update the Gemfile to use the version with the fix). |
@mlazari No, I just tested that branch and it did not fix the error when creating a cert. [19:27:13]: Error setting value '[]' for option 'cached_devices'[!] cached_devices parameter must be a non-empty array of Spaceship::ConnectAPI::Device |
That seems to come from a line in this PR: https://github.com/fastlane/fastlane/pull/21694/files#diff-e92862fddb614ea5aeca5cda382660111bf88e51f06781a88f963a20dbab47b1R223 which I think is the same that introduced this bug too, so could be related indeed. |
Your issue seems to be fixed in another PR #21766, can you try on that branch? |
I installed fastlane with homebrew. Is there any way to downgrade with brew? |
The branch was merged to master. |
Hey, thanks for fixing this issue! |
I could be completely wrong here but it looks like there is only one version available via brew:
I use gem to quickly install/test various versions of fastlane
|
to install an older version via homebrew you can do this:
uninstall via
as soon as you no longer need it. |
Don't bother, a new version (2.219.0) containing the fix was just released. |
See fastlane/fastlane#21762 and the CI failure we got for the first 24.2.0.0 deployment attempt.
New Regression Checklist
Regression Information
2.218.0
2.217.0
Regression Description
Complete output when running fastlane, including the stack trace and command used
The text was updated successfully, but these errors were encountered: