GPS, Timezone and IP Are Three Different Things: Testing Geo Behaviour on Real Phones
Short answer: you set your test phone's GPS to Paris, and your checkout still shows prices in Canadian dollars. That is because GPS is only one of the signals that say where a phone is. The server it talks to reads its IP address. The app reads its clock. The app store reads the account. If you want to see what a user in Paris sees, those signals have to agree on one city, and each one is set in a different place. This post goes through each signal, what it controls, how to set it on a real Android phone or iPhone, and how to check that nothing leaked.
The four signals and who reads them
| Signal | Who reads it | What it decides | How you change it |
|---|---|---|---|
| GPS location | The app, through the OS location API | Maps, store locators, geofences, "near me" | Mock location on the device |
| Exit IP address | Every server and CDN the phone talks to | CDN routing, region-locked content, regional prices on the web, fraud scores, consent banners | Send the traffic through a proxy in that country |
| Clock and timezone | The app and the OS | "Open now", delivery slots, date formatting, timestamps sent to your API | Change the device timezone |
| Language and region | The app and the OS | Strings, currency formatting, right-to-left layout | Change the device or app language |
Two more signals are worth knowing because they cannot be changed by any of the above:
- The SIM carrier. An app that reads the mobile network code still sees the real carrier, whatever the IP says.
- The store account. App Store and Google Play prices follow the country of the signed-in account, not the IP. A proxy will not show you the Japanese in-app purchase price.
Most "it works in testing but not for users in Brazil" bugs come from testing one signal and assuming the others followed.
Why the IP is the one you can't mock
GPS and API responses can be faked from inside your own test setup: you mock the location, or you intercept the response from your geo-lookup service and return a different country. That covers anything your app decides.
It does not cover decisions made before your code runs:
- CDN geo-routing. The CDN looks up the connecting IP and adds a country header, or sends the request to a different origin, before your server sees it.
- Region-locked content. Streaming and news sites block or swap content at the edge, by IP.
- Web pricing and currency. Many checkouts pick the currency from the IP on the first request.
- Fraud and bot scoring. Payment and sign-up providers score the IP's country and reputation, and compare it with the other signals.
To test those, the traffic has to actually leave from that country. That means a proxy.
Make the signals agree: a checklist
Use this whether you test on your own phones or in a device cloud.
- Pick one city, not one country. "US" covers six timezones. Choose New York, then use New York for everything below.
- Use a sticky session. Most proxy providers let you choose, in the proxy user name, whether the IP rotates on every request or stays for a session. Pick sticky. An IP that changes mid-test logs you out of most apps and looks exactly like fraud.
- Route the traffic, then check the exit IP from the phone itself. Open a what-is-my-IP page in the phone's browser, such as
https://ifconfig.co/json, and check the country and city. Checking from your laptop only proves the proxy works, not that the phone is using it. - Move the GPS to the same city. A phone whose IP says New York and whose GPS says Montréal is a common fraud signal.
- Move the timezone to the same city. Turn automatic timezone off first, or the phone puts it back.
- Set the language and region if the app or site reads them.
- Watch for traffic that skipped the proxy (next section).
- Undo everything afterwards. A phone left on a Tokyo proxy with a Tokyo clock is the next tester's mystery bug.
Doing it by hand on your own devices
- Android: Settings, Wi-Fi, the network, Proxy, Manual. This proxy setting has no user name or password field, so it only works with a proxy that authenticates by allowlisted IP. Timezone is under Settings, System, Date and time.
- iPhone: Settings, Wi-Fi, the network, Configure Proxy, Manual. This one takes a user name and password, but it is an HTTP proxy only. Timezone is under Settings, General, Date and Time, with Set Automatically turned off.
In both cases the proxy applies to that Wi-Fi network only. Mobile data still goes out directly.
socks5 or socks5h
If your provider gives you a SOCKS5 proxy, prefer the socks5h:// form where your tool accepts it. With socks5h, DNS lookups are done by the proxy, in the target country. With plain socks5, the phone or your tool resolves hostnames locally first, which can send it to a CDN node near you, not near the exit IP, and quietly undo the test.
Where traffic leaks past a proxy
A phone's proxy setting is a request, not a rule. Apps and system services that open their own connections can ignore it:
- Push notifications. Apple and Google push connections are long-lived system connections and usually go direct.
- DNS. Lookups made outside the proxy reveal your real location to the resolver and can pick the wrong CDN node.
- QUIC and HTTP/3. These run over UDP. An HTTP proxy only carries TCP, so UDP traffic either goes direct or fails.
- Apps with their own network stack. Flutter's default HTTP client does not read the system proxy setting. Games and video calls use their own sockets and UDP.
So "the browser shows a New York IP" is not proof that your app's traffic left from New York. If the behaviour you are testing comes from one of these paths, check that path specifically: watch the connections the phone opens while you use the app, and look for any that went straight to the internet.
Doing it on RobotActions
RobotActions runs real Android and iOS devices in our cloud, and we added proxy routing for this kind of test. You bring your own HTTP(S) or SOCKS5 proxy from any provider and pay them directly. We do not sell proxies. Paste it once in Settings, Proxies (in any of the usual formats, including a provider's host:port:user:pass line or a whole curl -x command), click Test to see the exit IP and city, and save it. The password is stored encrypted and never shown again. On a device, Location & Network applies it, checks it before the phone changes, and can move the GPS and timezone to the proxy's exit city in one click. On Android the exit IP is also read back from inside the phone. Releasing the device removes the proxy and puts GPS and timezone back. Proxy routing is on the paid plans.
AI agents get the same thing as MCP tools:
device_set_proxy udid, proxySecret: "nyc-sticky"
-> exitIp, exitLocation, deviceExitIp (read from inside the phone)
device_set_timezone udid, timezone: "America/New_York"
ios_set_proxy udid, proxySecret: "nyc-sticky", fullDevice: true
ios_set_timezone udid, timezone: "America/New_York"
ios_proxy_leak_check udid, seconds: 30
-> direct connections by destination: push, DNS, QUIC, other UDP/TCPOn iPhone, fullDevice: true is opt-in and sends every app and system service through your proxy, not just the ones that honour the proxy setting. While it is on, UDP traffic such as calls and some games stops. ios_proxy_leak_check watches for 5 to 60 seconds while you use the app and lists the connections that went around the proxy. Both proxy and timezone are cleared automatically when the device is released.
Try it
Ready to test on real devices?
Sign in with Google or GitHub and get real iOS and Android devices in your browser — free to try.