-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
[Android] Request write permissions for stats sharing #15298
Comments
@anthonypkeane Can you please confirm why the issue is marked as |
Reopening as @alexsafe confirmed this needs to be QA'ed |
@anthonypkeane can't have open issues in the milestone unless its release blocking. @alexsafe can you confirm if the issue is fixed with brave/brave-core#8557? Moving out of 1.25.x until confirmed. If this still needs to be fixed and should be part of 1.25.x need to have a PR done and get it uplifted to 1.25.x cc: @kjozwiak @bsclifton |
This comment has been minimized.
This comment has been minimized.
Probably a good idea to recheck these as it was reverted from |
Verification passed on OnePlus 6T with Android 10 running 1.26.50 x64 Beta build
Verification passed on Samsung Tab A with Android 10 running 1.26.50 x64 Beta build
Logged follow up issue #16221 |
Description
Not having the storage write permission already added results in a crash when trying to share stats
Steps to reproduce
3.1 Wait for one the blocked ads+ trackers tier numbers to be hit and press the share button on the tooltip.
Actual result
The app crashes with a permission error
Expected result
If the write permission is not set the user should be presented with a request permission to allow storage write.
The flow of the stats share feature should not be interrupted and the app should not crash.
(We need storage write permission to temporary store the image containing the stats in order be share it)
Issue reproduces how often
Easily reproduced
Version/Channel Information:
Device details
Brave version
1.25.13
Website problems only
Additional information
The text was updated successfully, but these errors were encountered: