Maps SDK and Location Data: What Play Actually Wants to Know
Embedding a maps SDK (Google Maps, Mapbox, or similar) almost always means declaring location collection, but the granularity matters: "precise" vs "approximate" location has a real difference in the form, and defaulting to the wrong one is a common inaccuracy.
Maps SDKs frequently request fine location by default even when your app's actual feature only needs approximate location (like showing a general area, not turn-by-turn navigation).
The fix
Fix: check whether your maps integration truly needs ACCESS_FINE_LOCATION or if ACCESS_COARSE_LOCATION covers your feature — narrower permissions mean a cleaner declaration.
The same check runs automatically when you upload your bundle to the AAB analyzer — permissions, SDK fingerprints, and version info in one pass, free.
Keep going
Run this check on your own AAB
Free analysis, exports when you need them.