-
-
Notifications
You must be signed in to change notification settings - Fork 18
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
question on permissions #41
Comments
Regarding android.permission.READ_PHONE_STATE: As we discussed sometimes in the past, I really do not know. It is not declared in the manifest file of this app, as well as in none of the manifest files of my own library (sCommon & RootFilePicker) that I am using. It could be declared in some external libraries that I used. Anyway, my app never ever uses that permission to monitor the call details of users (anybody can check the source code). The second permission should be acquired because my app declared "android.permission.WRITE_EXTERNAL_STORAGE" in the manifest, which is related to exporting/restoring De-Bloater profiles. |
eh, kinda over-specific dementi 😜 "does not use it" would suffice. Mind giving Removing Unwanted Manifest Permissions With tools:node a try there?
If it would have been implied, it would have a trailing asterisk – but it does not. It's nowhere in your code (according to a Github search at least), so it must have been dragged in by some dependency. Not sure which, though. Not many candidates, either. Funny, none of the two direct deps have it declared either… |
Just wanted to be clear :)
It is not necessary to declare "android.permission.READ_EXTERNAL_STORAGE" if "android.permission.WRITE_EXTERNAL_STORAGE" is declared (that is in our case). |
May I ask what
android.permission.READ_PHONE_STATE
andandroid.permission.READ_EXTERNAL_STORAGE
are requested for? The scanners here at IzzyOnDroid just reported them to me 😉 Thanks in advance!The text was updated successfully, but these errors were encountered: