How to test geofences on a real iPhone

Why test geofences on hardware

Geofences (Apple calls them condition monitoring, or region monitoring) are handled by iOS, not your app. The system watches your regions and wakes or relaunches the app when the user enters or leaves one. That behaviour, plus permission prompts and background limits, is exactly what the Simulator and unit tests don't show. Apple's documentation notes that if an iOS app isn't running when a condition is satisfied, the system tries to launch it, and that monitoring only starts after the user unlocks the device following a reboot (Apple: monitoring geographic regions).

A test plan that works

1. Save your test points. For each region, save a point well outside it and one well inside it as favorites in Geovo. "Well" matters: keep the points comfortably beyond the radius so GPS accuracy doesn't blur the result.
2. Start outside. Teleport to the outside point and give the app time to register its conditions.
3. Cross the boundary. Play a walking or driving route from outside to inside, or teleport straight to the inside point. Routes are closer to real life; teleports are faster for smoke tests.
4. Check the exit. Move back out the same way.
5. Repeat in the background and after a force-quit. This is where most geofence bugs live: the app must recreate its monitor when iOS relaunches it.
6. Repeat with different permissions: Always and While Using, and Precise Location on and off.

Make runs repeatable

• GPX and KML: import the same route file every run, or export a route you drew and commit it to your repo. Route formats explained.
• Loop and back-and-forth: let a route cross a boundary again and again for soak tests.
• Schedules: start a teleport or route at a set time while Geovo is open.
• Session track export: save exactly what was sent to the iPhone, with times, to attach to a bug report.

Core Location details worth knowing

• 20 conditions per app. Core Location stops any single app from monitoring more than 20 conditions at once (Apple). If your app rotates regions as the user moves, test the rotation by playing a long route.
• CLMonitor is the newer API (iOS 17+) for conditions, alongside the older region monitoring calls (Apple: CLMonitor).
• Simulated locations are detectable. Since iOS 15 an app can check whether a location was simulated by software (CLLocationSourceInformation). If your app rejects simulated locations outside debugging, test both paths deliberately; Geovo doesn't hide simulation.
• GPS only. Geovo changes the GPS position, not the IP address, so server-side geo-IP logic needs your backend's own test overrides.

Set up a test iPhone

1. Download Geovo on a Mac or Windows PC (Windows needs iTunes from apple.com for Apple's driver).
2. Plug in the test iPhone, tap Trust and turn on Developer Mode.
3. Save your test points, then teleport or play a route.
4. Optional: install the Geovo iPhone app so testers can run the same checks unplugged, on Wi-Fi or cellular.

Coordinates never leave your devices. Every feature is free for 30 minutes a day; for a release cycle, Pro is $5.99/week or $24.99 for 3 months. See pricing.