When publishing a package on the Google Play store, I get this warning:
Users that have the APK with version code xx may need to accept the android.permission.WRITE_EXTERNAL_STORAGE permission, which may result in them not upgrading to this version of the app.
I added WRITE_EXTERNAL_STORAGE in an array to expo.android.blockedPermissions but it still happens.
hi there! i’m not quite sure what’s happening there, perhaps it is a stale warning in the google play console?
if you set the buildType to apk on your build profile, you can inspect the permissions yourself. here’s an example, where i inspect the apk without the blockedPermissions config:
I went ahead and changed from AAB bundle to APK, with a new version code and release in the Google Play console, and the same is happening:
‘Users that have the APK with version code 99 may need to accept the android.permission.WRITE_EXTERNAL_STORAGE permission, which may result in them not upgrading to this version of the app.’
sorry my suggestion with the apk point was for you to manually inspect locally using aapt2 that your permissions are indeed what you expect. you should definitely use an app bundle on the play store
hey there! I see what the problem is now - it looks like the default expo-cli version on EAS Build needs to be updated. we’ll take care of that on monday. for now, you can add "expoCli": "5.4.4" to your build profile to ensure you’re using the latest release, and that will resolve your issue.
i downloaded the apk, ran aap2 on it to dump permission and confirmed that it does not include WRITE_EXTERNAL_STORAGE… so this could be an issue with play store, or you’re not submitting the correct build possibly. you should switch back to building an aab for submitting to the store, rather than apk.