A country flag on a phone does not prove that every regional signal agrees. Timezone, display language, GPS coordinates, and network egress are independent inputs. Apps may combine them with account settings or server-side rules.
Mobilebox supports timezone, locale, GPS location, and a supplied SOCKS5 proxy. The country shortcut sets a matching timezone, locale, and GPS location. It does not purchase or assign a country-specific IP address.
Configure the signal you mean
| Setting | Changes | Does not prove |
|---|---|---|
| timezone | Android timezone | Network origin |
| locale | Language/locale configuration | GPS location |
| location | Supplied GPS coordinates | Residential IP or physical presence |
| proxy | Network egress through your supplied proxy | Account region or app eligibility |
For a localized UI test, locale may be enough. For a timezone rendering bug, set timezone explicitly. If the task depends on network geography, supply and verify a suitable proxy rather than assuming GPS changes the IP address.
An explicit settings request
curl --fail-with-body -X PATCH "$MSB/v1/phones/$ID/device" \
-H "Authorization: Bearer $MOBILESANDBOX_API_KEY" \
-H 'Content-Type: application/json' \
-d '{"timezone":"Europe/Berlin","locale":"de-DE","location":{"lat":52.52,"lng":13.405}}'The API expects an IANA timezone and a BCP-47 locale. Changing locale restarts the UI, so observe again before reusing references or continuing a batch. Device settings survive park and start.
Verify from the application
Read GET /v1/phones/{id}/device for the configured device state. Then verify the outcome inside the target app. An app may cache its language, use an account-level preference, ignore location, or require permission before reading it.
A settings response proves what the service configured. It does not prove how a remote service interpreted it. Keep those two assertions separate in your test report.
Keep proxy credentials out of evidence
A proxy URL can contain a username and password. Use secret storage, avoid pasting it into prompts or public issue reports, and inspect logs and screenshots before sharing them. The API redacts proxy credentials from phone metadata, but that does not sanitize every artifact your own workflow creates. See the reference for supported fields.