This one is a bug report and an apology.
For background on the game and what Dispatch Zero is, start here.
How a Mission Gets Verified
When you reach a target in Dispatch Zero and take your proof photo, the app runs two checks. The hard one is GPS: were you actually standing within eighty meters of the place? The soft one is freshness: was this photo taken just now, or is it an old picture from your camera roll? For that second check, the app reads the timestamp your phone’s camera writes into every photo.
Here is the problem. Phone cameras record that timestamp in local time, whatever the clock on your phone says, and they don’t attach a time zone to it. The app assumed it was in UTC, the time at Greenwich. For anyone outside that one time zone, an honest photo taken on the spot looked hours old, or hours in the future, and was rejected.
If you were in Los Angeles, your fresh photo looked eight hours stale. In New York, five. In Paris, it looked like it had been taken an hour from now. Every one of those was turned away.
Why It Hid So Long
Two things went wrong.
First, my own testing kept passing. My automated test photos were stamped in UTC, and some phones strip the timestamp from a photo before uploading it, which the app deliberately forgives, because GPS is the real proof. So the check worked perfectly in every case I tried, and failed elsewhere.
Second, the failure was in character. When a photo doesn’t pass, Zero says “The proof is not yet sufficient, agent. Try again.” That’s good for the game and terrible for debugging: it sounds like the player did something wrong, not like the game is broken. To make it worse, the server was supposed to log the real reason for each rejection, and a separate logging misconfiguration meant those lines were quietly thrown away.
Since mid-June, nobody outside my own testing has completed a mission. People kept signing up and requesting dispatches. They just couldn’t finish.

To Our Agent in France
In early November, someone in France made it all the way to their target, Statue de la Sasson, and took their photo. Zero rejected it. They took another. Rejected. And another, and another: four attempts in a little over a minute, standing exactly where they had been sent, each one met with the same polite refusal.
If that was you: your proof was sufficient. It was always sufficient. You did everything right, and the game told you that you hadn’t. I’m sorry. Dispatch Zero doesn’t collect email addresses (we have a big privacy focus), so this post is the only way I have to tell you. Your file is still open, the statue is still there, and the mission should now accept your photo.
My apologies, this whole thing is a side project and needed better follow up to catch these errors.
The Fix
The app now works out which time zone your photo was taken in before deciding whether it’s fresh:
- From the photo itself. Most modern phones also record their time zone in the photo’s metadata. When that’s present, the app uses it.
- From your browser. When the photo doesn’t say, the app now sends along the time zone your phone’s browser reports.
- Benefit of the doubt. If neither is available, the photo passes as long as it would be fresh somewhere on Earth, which still rejects yesterday’s photo, without punishing anyone for where they live.
The GPS check is unchanged, and old photos are still rejected. The test suite now includes phones in Paris, New York, Los Angeles, Tokyo, Kathmandu (whose offset runs on a quarter hour), Adelaide, American Samoa, and Kiritimati, the first place on Earth to see each new day. And when a photo is rejected now, the server records why, the distance and the timing, never your location, so the next problem like this should take me minutes to find, not months.
Try It
If you gave up on a mission because Zero kept refusing your proof, I’d love for you to try again. And if it refuses you now, please let me know, I’ll be able to see why.




Comments
Join the conversation on Bluesky