How do ride-hailing teams test pickup pins and nearby driver states?
What teams actually do: prepare candidate pickup pins, offset points, no-stopping points, parallel roads, and venue entrances for…
Authorized iOS location testing
Authorized iOS location QA for developers and QA teams
WLOC is a browser-controlled, bounded location-testing workflow for iOS devices you own or are authorized to test. It is not a consumer Location Changer, a privacy VPN, or GPS hardware modification.
- For iOS developers and QA teams
- Devices you own or are authorized to test
- Browser-controlled, bounded location-testing workflow
- Not GPS hardware modification, a privacy VPN, or universal app compatibility
- Install a configuration Profile, connect VPN in iOS Settings, and review CA/system impact
- One free Tokyo Tower diagnostic; no card required
- Bought in the iOS app through the App Store; the price is shown before you confirm; 1 active device; Restore stays available
Sign in to check eligibility. If available, add an authorized iPhone, install the Profile, connect VPN, and confirm one fixed Tokyo Tower result yourself. No card required.
Child scenarios stay published for authorized QA of apps you own. This page is not a promise for attendance, games, ride-hailing abuse, finance, payments, identity, risk control, or circumventing rules.
Common location-testing needs
Common location-testing needs
Use WLOC when a team needs repeatable location states for QA, operations, research, review demos, or privacy checks while staying inside authorized devices, apps, accounts, and environments.
Use cases
Authorized iOS location QA for developers and QA teams
Browse practical workflows for check-in, virtual location, maps, routes, nearby features, geofences, and regional app behavior.
How can location-based games QA map states without jailbreak?
Game teams using WLOC typically prepare authorized points on development builds or test servers: dense resource cells, event…
How do travel apps preview city-specific content from one iPhone?
A team's actual workflow: save representative points for target cities and preview city content from one iPhone.
How can a weather app QA city and GPS fallback behavior?
QA teams use WLOC to prepare city-center, suburb, airport, and border points so teams can separate weather-data errors from…
How can an App Store review demo show location features clearly?
Seasoned developers prepare non-private demo points, a test account, expected screens, diagnostics, and recovery notes for an…
How can map SDK teams verify coordinate conversion issues?
SDK teams using WLOC keep the link, normalized coordinate, conversion result, and target-app display together.
How can civic or emergency apps test geofence messaging safely?
WLOC supports staging or explicitly authorized environments where teams can save safe geofence points and verify trigger, exit…
How can tourism AR guides test location-triggered content remotely?
Teams save attraction entrances, exhibits, viewpoints, and trigger-boundary points so authorized devices can preview AR content…
1-2-3 workflow
1-2-3 workflow
Pick or paste the target location and confirm coordinates.
Save the profile, copy the supported setup link, and keep the test within an authorized scope.
Run diagnostics, verify the target app behavior, then restore normal location behavior when the test is done.
Authorized testing only
Authorized testing only
Setup installs a device-specific configuration Profile, adds a CA root, and uses an IKEv2/VPN test tunnel. That is not a privacy VPN and does not require a separate third-party VPN app. WLOC does not modify GPS hardware and does not claim every third-party app will follow. Restore, Revoke, and Emergency Stop stay available.