-
Notifications
You must be signed in to change notification settings - Fork 762
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(android): hasWritePermission for SDK 33 #608
Merged
erisu
merged 7 commits into
apache:master
from
erisu:EYALIN-fix-android-13-hasWritePermission
Oct 17, 2023
Merged
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
4f70594
fix Android 13 write permissions
EYALIN 6fbfd99
Indent file
EYALIN 0111fd3
revert(android): changes previously made to getWritePermission
erisu 28318ff
refactor(android): simplify hasWritePermission and fix formatting
erisu dd1cdb2
fix(android): add comment suggestion to hasWritePermission
erisu ec7ab33
style(android): applied Android Studio code formatting
erisu bccbb55
fix(android): add comment suggestion to getWritePermission for extra …
erisu File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
What is happening here in the
else
case?Mostly asking because
getWritePermission
is always called providing acallbackContext
.Are we sure it does not wait indefinitely?
Is doing nothing really fine, or should
callbackContext
be called in every case, to guarantee the execution flow continues?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 think I "found" my own answer:
in current code, in the case of
Build.VERSION.SDK_INT >= Build.VERSION_CODES.TIRAMISU
,getWritePermission
is never called ...So my question does not really mater, even if strictly speaking it is probably a problem for the execution flow, indefinitely waiting for the
callbackContext
.Details:
getWritePermission
calls are always preceded by a check forneedPermission(nativeURL, WRITE)
, that will returnfalse
in this same given versions condition, becausehasWritePermission
was changed to always returntrue
for it.So, the
if (android.os.Build.VERSION.SDK_INT < Build.VERSION_CODES.TIRAMISU) {
added ingetWritePermission
is mostly useless, and should whether be removed or be fixed.