Spoofing Your Location in Google Play Store

Google Play storefront georestrictions are usually enforced by a mix of Play country / billing profile, network geolocation, and cached Play state — not only by the phone GPS. Therefore a VPN alone sometimes works, but in newer Play flows you usually also need to reset cached state and, for real country/profile switches, use an account/payment profile that matches the target country.

If your goal is only to obtain the APK for reversing, it is often easier to use the alternative acquisition workflow documented in Android Applications Pentesting instead of fighting the storefront.

What Google Play Actually Checks

Current network location (the country seen from the exit IP).
The Google Play country/profile attached to the account and Google Payments profile.
Cached state in com.android.vending, com.google.android.gms, and Download Manager.
Whether the package is published in that country by the developer.
In some cases, device certification / integrity (this is a different problem from pure region spoofing).

If an app is hidden because the device is not Play-certified or fails attestation, check Play Integrity attestation spoofing.

Fast Path on a Non-Rooted Device

Connect to a VPN endpoint in the target country.
Prefer a fresh test Google account already configured for that country. Reusing an account from another country often triggers the selected Play country matches your country of residence error.
Clear Play state from the GUI or directly with adb:

adb shell am force-stop com.android.vending
adb shell pm clear com.android.vending
adb shell am force-stop com.google.android.gms
adb shell pm clear com.google.android.gms
adb shell am force-stop com.android.providers.downloads
adb shell pm clear com.android.providers.downloads

Re-open Play Store and inspect Settings --> General --> Account and device preferences --> Country and profiles.
If the target country/profile appears, switch to it and retry the install. Google Play profile changes can take up to 48 hours to fully update.
If the country/profile does not appear, remember that Google expects you to be in the target country and to have a payment method from that country when creating a new Play country/profile.

Rooted / Emulator Workflow

When the target app checks GPS after installation, align the device geolocation with the storefront country:

Android Emulator: send a GPS fix directly to the emulator:

adb -e emu geo fix -3.7038 40.4168   # longitude latitude (Madrid)

Physical device: enable Developer options --> Select mock location app and set your GPS spoofer as the mock provider. If you need to do it from the shell:

adb shell appops set <MOCK_LOCATION_APP_PKG> android:mock_location allow

Bypassing App-Side Mock-Location Checks

Modern Android apps can detect lab GPS spoofing by calling Location.isMock() (API 31+) or the legacy isFromMockProvider(). On rooted labs, LSPosed modules such as HideMockLocation or a quick Frida hook are usually enough to neutralize these checks:

Java.perform(function () {
  const L = Java.use('android.location.Location');
  try { L.isMock.implementation = function () { return false; }; } catch (e) {}
  try { L.isFromMockProvider.implementation = function () { return false; }; } catch (e) {}
});

Keep the hook scoped to the target app when possible: the Play Store itself is mostly country/profile/IP driven, while the installed app is the component that commonly performs the GPS/mock-location check.

Common Failure Modes