Hello,
We are currently trying to get promoted by Google. In the process, Google found a few permissions that we need to document for them. One such permission was READ_EXTERNAL_STORAGE, which we have no where in our build.settings.
Why might they find this permission when we haven’t added it to our project ourselves?
Thank you!
Hello,
We are currently trying to get promoted by Google. In the process, Google found a few permissions that we need to document for them. One such permission was READ_EXTERNAL_STORAGE, which we have no where in our build.settings.
Why might they find this permission when we haven’t added it to our project ourselves?
Thank you!
Certain plugins may add permissions. You may want to post the list of plugins in use.
Edit: I noticed your have corona enterprise so this would not affecting if you are building though android studio and Xcode vs corona simulator
Any ads plugin would add this permission
@Scott Harrison and @SphereGameStudios,
Thank you for your response!
I may have found the true root of the issue, which relates to this post.
Although we didn’t have READ_EXTERNAL_STORAGE, we did have WRITE_EXTERNAL_STORAGE. According to that post, when WRITE_EXTERNAL_STORAGE is used, READ_EXTERNAL_STORAGE is implicit.
Exactly, ads write to external storage but then they have to read from it… common sense really 
I’m just curious. Do you actually see READ_EXTERNAL_STORAGE in your final APK’s Android manifest (you shouldn’t)?
You can use apktool to decompile the APK.
The reason I’m asking is because if you *do* see READ explicitly in the manifest then some more investigation is required.
If not, then everything is OK and Google is just flagging the implicit READ from the WRITE permission.
Hello,
We are currently trying to get promoted by Google. In the process, Google found a few permissions that we need to document for them. One such permission was READ_EXTERNAL_STORAGE, which we have no where in our build.settings.
Why might they find this permission when we haven’t added it to our project ourselves?
Thank you!
Certain plugins may add permissions. You may want to post the list of plugins in use.
Edit: I noticed your have corona enterprise so this would not affecting if you are building though android studio and Xcode vs corona simulator
Any ads plugin would add this permission
@Scott Harrison and @SphereGameStudios,
Thank you for your response!
I may have found the true root of the issue, which relates to this post.
Although we didn’t have READ_EXTERNAL_STORAGE, we did have WRITE_EXTERNAL_STORAGE. According to that post, when WRITE_EXTERNAL_STORAGE is used, READ_EXTERNAL_STORAGE is implicit.
Exactly, ads write to external storage but then they have to read from it… common sense really
I’m just curious. Do you actually see READ_EXTERNAL_STORAGE in your final APK’s Android manifest (you shouldn’t)?
You can use apktool to decompile the APK.
The reason I’m asking is because if you *do* see READ explicitly in the manifest then some more investigation is required.
If not, then everything is OK and Google is just flagging the implicit READ from the WRITE permission.