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
[screengrab] Permission Issues on API > 21 #17006
Conversation
Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). 📝 Please visit https://cla.developers.google.com/ to sign. Once you've signed (or fixed any issues), please reply here with What to do if you already signed the CLAIndividual signers
Corporate signers
ℹ️ Googlers: Go here for more info. |
@googlebot I signed it! |
CLAs look good, thanks! ℹ️ Googlers: Go here for more info. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a great fix! Clean solution for a problem affecting multiple users for a long time 💪
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is 🔥 Thanks, Greg! ❤️ You my hero
Hey @Gregadeaux 👋 Thank you for your contribution to fastlane and congrats on getting this pull request merged 🎉 Please let us know if this change requires an immediate release by adding a comment here 👍 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Congratulations! 🎉 This was released as part of fastlane 2.156.0 🚀
@Gregadeaux @joshdholtz It is occurred when using the device with API level 24 Error log is below |
@Thangaraj-M Do you mind create a new separate issue for this so that we can track the fix separately? 😊 Thank you! |
@joshdholtz I have created new issue for this. #17119 |
Checklist
bundle exec rspec
from the root directory to see all new and existing tests passbundle exec rubocop -a
to ensure the code style is validMotivation and Context
Fixes #15788
Description
Added
run-as
to commands that are accessing the possible screenshots directories to avoid permission failures. Created an empty Android project using the "Basic Activity" template. Implemented the test case described in the Screenshots documentation that takes two screenshots. Tested on 2 emulators, one running Android 21 and one running Android 28.Testing Steps