-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Supply action throws an error when uploading it with the mapping file #8187
Comments
It seems like you have not included the output of To make it easier for us help you resolve this issue, please update the issue to include the output of |
Here you go:
|
This looks similar to an error I thought I fixed a while ago (#7763). What version of Fastlane are you using? I think this should be fixed in 2.6.0+ Check the version of the google-api-client gem you have installed. You need at least 0.9.20, which the gemfspec for Supply should be installing. (But maybe you ended up with an old version somehow?) |
Yeah you were right! The fastlane version was 2.14.2 but the google-api-client gem is 0.9.11. Updating everything now, could it be because I was using "gem update fastlane" specifically? Thanks for your help! |
Hmm - that's odd. I'm not familiar enough with ruby to understand exactly why that would fail to update. :-/ Glad it's working for you, at least, though! |
New Issue Checklist
Issue Description
When using the supply action with a mapping file, it throws a NoMethodError in
/usr/local/lib/ruby/gems/2.3.0/gems/fastlane-2.14.2/supply/lib/supply/client.rb:223: undefined method upload_edit_deobfuscationfile
The method in question:
Changing validate_only to false still gives the same error. When the mapping line is removed the method doesn't throws any error.
Complete output when running fastlane, including the stack trace and command used
Environment
Please run
fastlane env
and copy the output below. This will help us help you 👍If you used
--capture_output
option please remove this block - as it is already included there.It seems with only an android aplication the fastlane env doesn't produce a succesful output:
The text was updated successfully, but these errors were encountered: