Skip to content
WLOCAuthorized iOS location testing

Authorized iOS location QA for developers

How can map SDK teams verify coordinate conversion issues?

Map SDK location errors often come from coordinate-system mismatch, not GPS.

Solution

Solution

SDK teams using WLOC keep the link, normalized coordinate, conversion result, and target-app display together. That makes it easier to compare basemap position, API output, and in-app pin behavior. Save links, coordinates, screenshots, and diagnostics so future releases can catch conversion regressions.

Problem

Problem

Map SDK location errors often come from coordinate-system mismatch, not GPS. WGS84, GCJ-02, BD-09, provider links, and app-side transforms can put the same landmark hundreds of meters apart. Compare WGS84 and GCJ-02 on a fixture you control; the legal boundary does not move and this page does not redraw a cadastral line.

Use WLOC in 3 steps

Use WLOC in 3 steps

  1. Pick landmarks where offset is obvious.

    Use plazas, bridges, park gates, campus entrances, or other visually identifiable places.

  2. Compare coordinate-system output.

    Check WGS84, GCJ-02, BD-09, map link parsing, and target-app pin placement side by side.

  3. Add offset samples to regression tests.

    Save links, coordinates, screenshots, and diagnostics so future releases can catch conversion regressions.

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.

Related scenarios

Conversion neighbors compare WGS84 and GCJ-02 on a fixture you control; they do not move a legal boundary.