ZYRNTOPOSend feedback
Goes straight to the developer — not a ticket queue.
Found a bug, or want to suggest something? Tell us below. If you are reporting a problem, the most useful thing you can include is what you were doing right before it happened, and whether it happens every time.
You can also email [email protected] directly — the same address, and the same person reads it.
What makes a report useful
A report gets fixed faster when it can be reproduced. You do not need to write much — four short lines beat a long description, because they let the same failure be triggered here on purpose:
- What you did. The steps right before it went wrong, in order. “Downloaded an offline area, went into aeroplane mode, reopened the app” is enough.
- What you expected. Sometimes the app is working as designed and the design is the bug. Saying what you expected is what separates the two.
- What happened instead. The exact wording of any error message, if there was one.
- Whether it happens every time. A problem that repeats on demand is usually fixed in a day. One that happened once, months ago, often cannot be found at all.
If the app opened this page for you, the App details box above is already filled in with your version, platform and device.
That is the single most useful line in a report: it rules out bugs already fixed in a later build. It is yours to edit or clear before sending.
Things worth checking first
A few reports arrive often enough to be worth answering here:
- Maps blank with no signal. Offline maps cover the areas you saved before you left, not everywhere you pan to. The documentation covers saving an area and checking what is stored on the device.
- A location is off by a consistent distance. This is almost always a coordinate format or datum mismatch rather than a GPS fault — check which format the readout is set to before reporting it.
- Team Sync will not connect. Connecting is the switch; there is no second visibility toggle to find. If a server is refusing you, the TAK server guide covers running your own and what the relay expects.
- A purchase has not unlocked Pro. That is a billing question rather than a bug — the refund policy explains who to contact depending on where you bought, which is faster than this form.
What happens after you send
The message goes to one developer, who reads all of them. There is no ticket number, no auto-reply and no support tier — the trade-off is that nothing gets lost in a queue, but a reply is not instant either.
Leaving your email is optional. It only matters if a question needs asking to reproduce the problem — without it the report is still read and still acted on, you just will not hear back.
It is used to reply about this report and nothing else, and is never added to a mailing list. The privacy policy sets out what is stored.
Fixes ship in the next release rather than individually. If you want to see whether yours has landed, the downloads page always carries the current build for every platform.
Security reports
Found something with security or privacy consequences — anything touching licence validation, account access or another user's location data? Email [email protected] directly rather than using this form.
Please say what you found instead of posting it publicly first. It reaches the same person, and reports like these go to the front of the queue.