Please provide the following:
- SDK Version: 40
- Platforms(Android/iOS/web/all): Android
- Add the appropriate “Tag” based on what Expo library you have a question on.
I am fighting with Google against their new storage permissions policy. They refuse to reply to my appeal requests on the Play Store (for more 2 weeks now) to discuss what the actual issue is.
So I am now on my own, figuring out if I am at fault and for what actual reason.
My app is getting rejected because, apparently, I am using the
MANAGE_EXTERNAL_STORAGE permission. However, I am not using such permission, and it is not declared in the app manifest.
After the first rejection I have also tried adding the following in
android/app/src/main/AndroidManifest.xml to make sure that such permission never ends up in the final build:
<uses-permission android:name="android.permission.MANAGE_EXTERNAL_STORAGE" tools:node="remove" />
And as I have verified on the uploaded appbundle on the Play Store, this permission does not appear in the list of required permissions.
Still, my app is getting rejected for this permission, explicitly:
I have analized all the packages used in my app, all the permissions they require, and I have determined that the only possible issues may come from the
expo-image-picker package. I am using Expo SDK 40, in bare workflow.
The additional instructions for Android say that the lib requires the
WRITE_EXTERNAL_STORAGE permissions, even for the latest Expo SDK 43.
No other package in my app requires any storage related permissions.
I am not using the
requestLegacyStorage option since Google’s policy requires builds to target at least Android SDK 30 (Android 11), where this option is ignored (as I understood it, it was accepted for apps targetting up to Android SDK 29, but not further - did I get this wrong ?).
What I don’t know is whether the
WRITE_EXTERNAL_STORAGE permissions are actually the same as
Can someone knowledgeable with Android permissions help me figure out this issue?
Do the permissions above count for the app rejection?