Skip to content
WLOCAuthorized iOS location testing

Authorized iOS location QA for developers

How can tourism AR guides test location-triggered content remotely?

Tourism AR guides depend on exact attraction points, route context, trigger radius, language, and unavailable states.

Solution

Solution

Teams save attraction entrances, exhibits, viewpoints, and trigger-boundary points so authorized devices can preview AR content remotely. This reduces onsite rework and catches mismatched content before visitors arrive. Record coordinate, content ID, app screenshot, and diagnostics, then restore normal location behavior.

Problem

Problem

Tourism AR guides depend on exact attraction points, route context, trigger radius, language, and unavailable states. Testers and content editors cannot revisit every scenic spot whenever narration or trigger rules change. Stand on a placemark you published; do not promise every third-party lens will lock or that a visitor’s live camera will overlay the same POI.

Use WLOC in 3 steps

Use WLOC in 3 steps

  1. Save attraction, exhibit, and boundary points.

    Store each trigger point and its outside-radius counterpart instead of testing only the park center.

  2. Preview AR content point by point.

    Check narration, images, route prompts, language, content ID, and unavailable messages against the location.

  3. Send trigger issues to content owners.

    Record coordinate, content ID, app screenshot, and diagnostics, 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.