We have 10 learning apps that have been in mobile stores for over 12 years and make 7 figure revenue yearly (we are legit, though not Epic). They are all the same code base and utilize the same permissions etc, just vertical specific assets and content.<p>Our 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).<p>We recompiled, submitted again indicating that we don't use the permission, but were rejected immediately again (likely an automated test).<p>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.<p>The whole situation is bizarre and we haven't been able to speak / email with anyone at Google to resolve it.<p>Has anyone run into a similar situation? Tips for actually getting to someone that could help get us out of this catch 22 loop?
One thing to checkout is perhaps some plugin/module you have might be adding this permission without you knowing about it.<p>Trying using the 'Merged Manifest' in Android Studio (<a href="https://developer.android.com/build/manage-manifests#inspect_the_merged_manifest_and_find_conflicts" rel="nofollow">https://developer.android.com/build/manage-manifests#inspect...</a>) to see if you can see coming from anywhere.