Skip to content
WLOCAuthorized iOS location testing

Authorized iOS location QA for developers

How can location-based games QA map states without jailbreak?

Location-based games combine map cells, resource refreshes, event zones, cooldowns, range prompts, cold-start positioning, and recovery after errors.

Solution

Solution

Game teams using WLOC typically prepare authorized points on development builds or test servers: dense resource cells, event entrances, boundary edges, no-content cells, and recovery locations. A test account can verify refresh timing, event entry, range copy, cooldown display, and error recovery as owned-environment QA, without touching live competitive fairness.

Problem

Problem

Location-based games combine map cells, resource refreshes, event zones, cooldowns, range prompts, cold-start positioning, and recovery after errors. Testing only the device's real location leaves remote event areas, empty cells, edge cells, and restore points untested, so player reports can be hard to reproduce.

Use WLOC in 3 steps

Use WLOC in 3 steps

  1. Collect the test-server map points.

    Save event zones, resource-dense cells, edge areas, no-content cells, and recovery points.

  2. Verify triggers with a test account.

    Check resource refresh, event entry, range prompts, cooldown display, and error recovery against the design.

  3. Keep evidence and return to real location.

    Record coordinates and game state only inside the authorized test scope, then restore normal location behavior.

Important boundary

Important boundary

WLOC is not a jailbreak. The current testing Profile includes a certificate and a VPN tunnel, and it does not require a separate third-party VPN client. Saving a target, Gateway acceptance, or a submitted Restore does not mean the target app adopted the location or that the device is already restored. WLOC does not promise to override every app's permissions, cache, or anti-cheat checks.