Google Play adding permissions we don't use, then failing us for lacking reason
7 points by MobileVet 5 months ago | 2 commentsOur recent Google Play update submission was failed on a single app because they said we weren't filling out the reasoning for camera / photo permissions (READ_MEDIA_IMAGES, READ_MEDIA_VIDEO). The catch is that we do NOT use those items, nor did we include the request for that permission (and all the other apps passed).
We recompiled, submitted again indicating that we don't use the permission, but were rejected immediately again (likely an automated test).
We force removed a permission that is tangentially related (though not the one indicated), recompiled and resubmitted. Oddly, the permission reappeared AND we subsequently failed again.
The whole situation is bizarre and we haven't been able to speak / email with anyone at Google to resolve it.
Has anyone run into a similar situation? Tips for actually getting to someone that could help get us out of this catch 22 loop?
- stephenheron 5 months agoOne thing to checkout is perhaps some plugin/module you have might be adding this permission without you knowing about it.
Trying using the 'Merged Manifest' in Android Studio (https://developer.android.com/build/manage-manifests#inspect...) to see if you can see coming from anywhere.
- MobileVet 5 months agoThanks for the suggestion. We’ll give it a shot
- MobileVet 5 months ago
- 5 months ago