What does GPSLarp actually change on my iPhone?
You are about to let a program on your Mac reach into your phone, and you would like to know what it does to the phone before you run it.
One thing changes: the position iOS reports as the device's location. No jailbreak. No app installed on the phone. No configuration profile. The only thing put onto the phone is a support package Apple publishes, mounted until the phone next restarts.
01The one value that changes
GPSLarp runs on the Mac and stays there. It talks to the iPhone through Apple's own device-development services — the same ones Xcode uses, over the same protocol — and sets the position the phone reports as its location.
That value is held by the system rather than by any single app, so an app that asks the system where it is reads that value the way it reads a real GPS fix — it is not modified and is not asked to cooperate. That is a description of the mechanism and not a promise about anyone's checks: some apps run their own and enforce their own terms against location spoofing regardless of how it was done. No immunity from another company's policy is offered here, because none can be.
The change lasts exactly as long as the Mac holds the connection. Stopping in the app, quitting it, or unplugging the phone ends it immediately — the three routes are on how do I put my real location back.
02What does not happen
This is the list people are searching for, so here it is plainly rather than folded into a paragraph.
- No jailbreak. iOS is not modified in any way. Nothing about the phone's security model is altered by GPSLarp.
- No app is installed on the iPhone. There is nothing to find on the Home Screen and nothing to delete. The software you downloaded runs on the Mac.
- No configuration profile is installed. There is no entry in Settings afterwards to hunt for and remove, because none was ever created.
- No file of ours is written to the phone at all. The override exists only while the Mac is connected and holding it, and the app stops asserting it the moment that ends, with nothing to clean up. What the phone reports afterwards is a question nobody here has measured — see what this page cannot tell you.
- Your iPhone passcode is typed into the iPhone. It is never typed into GPSLarp and it never reaches the Mac.
- Your Mac's administrator password goes into macOS's own dialog, which macOS draws and GPSLarp cannot read. It is never seen, stored or sent by us — that prompt and what it starts are on why GPSLarp asks for your administrator password.
03What stays on the phone, and whose it is
Three things do remain afterwards. All three are Apple's rather than ours, all three are things you agreed to on the phone, and all three are reversible from the phone without the Mac and without GPSLarp.
- A support package from Apple, until the phone next restarts. Before iOS will answer the services GPSLarp uses, it wants a developer disk image mounted — Apple's file, fetched from Apple, matched to the exact iOS build. GPSLarp asks iOS to mount it for you. It is the one thing in this list that is genuinely put onto the phone, and it is also the shortest-lived: restarting the phone clears it, which is why the same request reappears after a reboot. My iPhone is missing a file iOS needs first has the detail.
- The trust pairing between the phone and the Mac. It is the same pairing Xcode creates, it is what lets the two devices talk at all, and it stays until you clear it. The reset that removes it is on my iPhone won't trust this computer — read what it costs first, because it clears every computer the phone has ever trusted.
- Developer Mode, if you turned it on. It survives restarts by design; that is Apple's decision, not a leftover. Turning it off is Settings › Privacy & Security › Developer Mode, off, then restart. Developer Mode isn't showing on my iPhone covers both directions.
Neither of those is evidence of anything
A trust pairing and a Developer Mode toggle are what a phone looks like after somebody has done ordinary development work with it. They are not records of what was done, and GPSLarp writes nothing alongside them.
04Where this is meant to be used
On devices you own, and not to deceive people who are relying on your real location for their safety. That line sits at the bottom of every page on this site, and it is the one thing about this product that is not a technical question.
The terms are the contract, and the privacy policy lists every service the app contacts from your machine. Neither is long.
05What this page cannot tell you
Whether an app can tell. The value is changed at the system level, so an app reads it the way it reads a real fix. That is a description of the mechanism and not a promise about anyone's checks: some apps run their own and enforce their own terms against location spoofing regardless of how it was done. No immunity from another company's policy is offered here, because none can be. Decide what that means for you before relying on this for anything that matters.
Whether the location holds. Nobody has measured whether a location set by GPSLarp stays put. There is deliberately no page on this site about that, and there will not be one until somebody has measured it — a confident page about a defect this product may or may not share would be an invention, and the reader is the one who would pay for it.
Whether it works on your phone. Nobody in this project has watched a location change happen on a real phone from end to end. Everything above describes what iOS requires and what this application does, which is a smaller and more specific claim than the one you probably came here to have confirmed. If the position on the phone does not move, I picked a place and my iPhone's location didn't change has the points where the chain breaks, and will GPSLarp work with my Mac and my iPhone? has what has to be true before you start.