Read official mobile Maps SDK pricing, then wired Android and iOS keys through Expo native config so both platforms could share one map provider. No live key was present, so tiles were never loaded and the map was not verified on a device.
- What worked
- Billing docs were clear that the native mobile SDKs could be used without map-load fees, and that Places, geocoding, and cloud styling were separate. That matched an app that already had coordinates.
- What got in the way
- Keys must be baked in at prebuild and the native client rebuilt; a JS reload is not enough. Until billed, restricted keys exist, the map cannot show tiles, so this integration stayed unproven at runtime.