Create and preview a route before you start playback

Open Routes and add a route

Open the Routes tab and tap the add button. Give the route a recognizable name so you can reuse the same QA path later.

• A route stays in the on-device Route Library.
• Use a name that describes the path and expected test result.

Add at least two points or import GPX

Tap the map to add waypoints, add the current coordinate, use the two-point starter, or switch to GPX import. WLOC shows the point count, total distance, and estimated duration while you edit.

• Two points are the minimum; additional waypoints are supported.
• Each waypoint can keep a name, wait time, and optional segment speed.

Preview the path without changing the device

Use Route Preview to watch the selected route on the map. Replaying the preview recalculates the local animation; it does not write a route or test location to the device module.

• Preview first to catch a wrong point or unrealistic speed.
• The preview is a planning tool, not proof that a target app followed the route.

Choose speed, loop behavior, and accuracy

Pick a walking, running, cycling, or driving preset, or set a custom speed. Turn on loop playback when the path should repeat; reverse-on-loop makes every second pass run in the opposite direction.

• Distance and estimated duration update with the route settings.
• Accuracy describes the network-location sample and does not improve GPS hardware.

Run Change Location diagnostics, then start

Routes use the same current testing Profile as a single test location. That Profile includes a certificate and a VPN tunnel and does not require a separate third-party VPN client. Read diagnostics as observations before tapping Start Route. They are not proof a target app adopted the route.

• A separate route diagnostic is not required.
• Start is disabled when the shared device-write gate is not ready.

Pause, resume, stop, and restore

While a route is running, you can pause, resume, or stop it. When the authorized test is finished, stop the route, clear any remaining test target, or submit Restore. A stopped route, passthrough status, or submitted Restore is not proof the iPhone or the target app is already back.

• Stopping route playback and submitting Restore are separate actions.
• Keep a screenshot of what the target app shows. That record is not proof by itself.

What each route setting changes

• Waypoints — The ordered points WLOC moves between; at least two are required.
• Speed — The planned movement speed used to calculate the route timeline and estimate.
• Wait time — An optional pause at a waypoint before playback continues.
• Loop — Repeats the route after the last point; reverse-on-loop alternates direction.
• Accuracy — The accuracy value attached to the network-location samples, not GPS precision.

Route playback is not a GPS track simulator

The current testing Profile includes a certificate and a VPN tunnel and does not require a separate third-party VPN client. Strong GPS, target-app cache, permissions, IP or account rules, and server-side decisions can produce a different result. Use Routes only on devices, apps, accounts, and networks you own or are explicitly authorized to test.

Plan the route first, then start a reversible test

Create or import a route, read the preview and diagnostics as observations, and start only inside an authorized test. Submit Restore when finished. A submitted Restore is not proof the iPhone or the target app is already back.