WLOC

Use cases

How can an App Store review demo show location features clearly?

App Store reviewers need to understand why an app uses location. If the review build opens to a default city, an empty list, an unavailable venue, or a location-failure fallback, the core feature can look broken even when the production pa…

Open in the App Store All use cases

Problem

App Store reviewers need to understand why an app uses location. If the review build opens to a default city, an empty list, an unavailable venue, or a location-failure fallback, the core feature can look broken even when the production path is configured correctly. Verify Choose fixed review demo locations., Pick non-private demo points and record the expected in-app state for each one., Write the demo path into review notes., Include the test account, target point, expected screen, and restore instructions so the reviewer does not have to guess..

Solution

Seasoned developers prepare non-private demo points, a test account, expected screens, diagnostics, and recovery notes for an authorized review flow. The review packet should explain what each location demonstrates and state that the demo respects iOS permissions and the target app's own checks.

Use WLOC in 3 steps

  1. 1Choose fixed review demo locations.Pick non-private demo points and record the expected in-app state for each one.
  2. 2Write the demo path into review notes.Include the test account, target point, expected screen, and restore instructions so the reviewer does not have to guess.
  3. 3Run the exact demo before submission.Confirm the review build still shows the expected state and keep diagnostics plus support links ready.

Important boundary

WLOC is not a jailbreak. It does not install system certificates. It does not include a VPN. And it does not promise to override every app's permissions, cache, or anti-cheat checks.