Diagnostic fix · System cache
Diagnostics passed, but the location still won't change?
WLOC confirms that a compatible network response was patched, but the target app still shows an old or real location. A patch is evidence for one layer, not proof that iOS or the target app accepted it. Check freshness, app cache, permissions, GPS conditions, and app-specific rules in order.
Plain English
Why this happens
iPhone location results can combine GPS, Wi-Fi and cellular positioning, Bluetooth, permissions, recent system state, and the target app's own cache or server-side logic. WLOC diagnostics can prove a fresh compatible request and patch on the supported network path. They cannot prove which signal the target app ultimately used. Treat request time, patch time, permission state, app refresh, and the observed target-app result as separate evidence.
Step 1：Prove that the request and patch are fresh
Run diagnostics again and compare the latest request and patch timestamps with the moment you reopened the target app. If they did not advance, fix the compatible client, scoped HTTPS setup, or request path first. If both advanced, continue with an app refresh and permission check. Restart the authorized test device only as a later stale-state escalation; Apple does not publish a WLOC-specific rule that a restart is mandatory on iOS 26 or later.
- A VPN icon alone is not proof; check the latest request and patch times
- No fresh request: reopen the target app and review its location permission
- Fresh request but no patch: return to the setup and certificate checks
- Fresh patch but stale result: continue with app refresh, permissions, and controlled signal comparison
Step 2：Force quit the target app completely
The app you're testing (Maps, food delivery, ride-hailing, dating apps, etc.) may have cached its own last-known location. Swipe up from the bottom of the screen (or double-press Home) to open the app switcher, then swipe the target app up and away to fully close it. Then reopen it. This forces the app to request a fresh location from the system rather than using its internal cache.
- Swipe up from bottom → find target app → swipe it away
- Do NOT just go to the home screen — that keeps the app running
- Reopen the app after force-quitting; it will request a fresh location
Step 3：Refresh the target app's location permission
On an authorized test account, open Settings → Apps → [target app] → Location and review the current permission. If the test calls for a fresh prompt, choose 'Ask Next Time or When I Share', reopen the app, and grant only the access the scenario requires. This can trigger a new location request, but it does not guarantee that the app will discard every cache or prefer the patched network result.
- Record the permission before changing it
- Reopen the app and watch whether the WLOC request timestamp advances
- Restore the original permission after the test
- Treat a fresh permission prompt as evidence, not a guaranteed cache reset
Step 4：Compare a controlled indoor condition
If fresh requests and patches are confirmed, repeat the authorized test in a stable indoor location and record the result. GPS and other signals can affect the outcome, but there is no universal priority rule that guarantees the network result will be selected. Keep the account, permission, target, and app state unchanged so the comparison answers one question at a time.
- Use the same target, account, permission, and app version
- Record request time, patch time, and the target-app result
- Do not infer the active sensor from the status-bar arrow alone
- If results differ, report the condition as evidence rather than a universal fix
FAQ
Why does the result change between attempts?
The request may not be fresh, the target app may reuse its own state, permissions may differ, or other location and account signals may contribute. Compare one controlled condition at a time and keep the WLOC timestamps with the observed result.
Can the status-bar arrow prove that GPS overrode WLOC?
No. The arrow shows that an app recently used Location Services; it does not identify the final sensor mix or prove why a target result was chosen. Use it only as context alongside diagnostics and app evidence.
Should I test with CarPlay or an external location source connected?
Prefer a controlled iPhone-only test unless that connection is the feature you are explicitly authorized to verify. External or vehicle-provided location conditions add another variable and should be documented separately.
WLOC
Fresh timestamps turn a vague failure into a specific next step.
WLOC verifies one compatible network-location layer. Compare the request, patch, permission, app refresh, observed result, and recovery separately so the report shows what happened without claiming a universal iOS cache rule.