-
Notifications
You must be signed in to change notification settings - Fork 343
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
fix: Fenix does not require WRITE_EXTERNAL_STORAGE permission to be granted #2306
fix: Fenix does not require WRITE_EXTERNAL_STORAGE permission to be granted #2306
Conversation
@Rob--W this is currently mainly a draft of the kind of fix we may use and then even release on npm in a minor version: the idea is to only make the check for the read permission still mandatory, and instead only run a "non blocking" check for the write permission (which just log a debug message, to avoid confusing the user with a warning message that is unlikely to apply to most users nowdays, but still allow us to get it in the verbose logs if we are investigating an issue reported to us). Let me know wdyt. |
Codecov Report
@@ Coverage Diff @@
## master #2306 +/- ##
=======================================
Coverage 99.88% 99.88%
=======================================
Files 32 32
Lines 1699 1699
=======================================
Hits 1697 1697
Misses 2 2
Continue to review full report at Codecov.
|
4fb8db1
to
e828938
Compare
// on android versions >= 23 (Android Marshmallow, which is the first version where | ||
// these permissions are optional and have to be granted explicitly). | ||
// Runtime permissions needed to Firefox to be able to access the | ||
// xpi file uploaded to the android device or emulator. | ||
const requiredPermissions = [ | ||
'android.permission.READ_EXTERNAL_STORAGE', |
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.
I just tested, and the read permission isn't even needed to run an extension in Fenix. We can delete lots of code.
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.
@Rob--W have you checked that the permission wasn't actually already granted?
some more details about what STR you actually tested manually would be helpful to assess if that was enough to ensure we are not missing some legit corner case.
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.
@Rob--W also, I would like to release this into a minor or patch version, and so "less changes" would make me feel way less concerned about releasing it in a "non major" new release (than "remove a lot of code").
I would be obviously more than happy about "remove a lot of code" in a separate follow up.
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.
Filed #2312
Fixes #2304
For Fenix we don't need the WRITE_EXTERNAL_STORAGE permission to be granted:
web-ext run
was also running it in a separate temporary profile as we do on desktopweb-ext run
uploads to the android emulator or deviceTODO:
add a more specific test case for the behavior expected