Reports and bug reports#
Three situations in which we want to know what happened: the app closed itself, something in the city does not add up, and a pause on touring appeared on the screen. This page says what to do in each of them and what never to send us.
A bug report from the app#
When the app falls over, it saves an error report on the phone — you do not have to tap anything to keep it.
- Open the Profile (bottom bar) and tap the Error reports row. The subtitle under it says how many reports are lying on the phone.
- At the top is the Latest report, with older ones under it — the app keeps the three newest ones and quietly deletes older ones.
- Every report shows what comes in useful for a diagnosis: the app Version, the Time of the event, the Device, the Android version and the Beginning of the stack trace. A report from a crash at launch additionally carries the words Crash during app startup.
- With the Copy report button you drop the whole report into the clipboard (the app confirms it with a short message).
Reports are sent by themselves at app startup, when you are logged in — you do not have to send them anywhere, and nothing is lost if you have no internet at that moment.
| What you see by the report | What it means |
|---|---|
| Sent to the server | The report reached us. The file stays on the phone so that you can still look at it. |
| Waiting to be sent (no connection or an older server) | We will try again at the next app startup. |
| No reports | Since installation the app has not recorded any crash. |
A problem with the content: a missing stop, a wrong location, a typo#
The channel that really exists is error reports from the app (the section above) — we do not yet have a public contact form or an e-mail address for players, so we do not promise one here until it works.
Reports about the content we handle on our side: they go into our content back office, where fixes are planned together with the next walks around the city. Before you report anything, it is worth checking two things:
- whether the stop really belongs to the route you are walking — the list of stops is in the route panel, under the Browse stops button (Route stops),
- whether you are looking for the marker according to how it looks — shapes and colours are told apart in Map legend.
A missing stop, a shifted marker or a typo in a description never block your touring: you can walk on, and we will make the fix in the city's content.
Touring paused for a fake location#
The app watches whether the position really comes from this phone's GPS. When it detects a swapped location (for example, a GPS-emulating app is running), it shows the Walks paused screen with the Back on the map in … counter — until the pause ends you will not start a route, complete a stop or collect a find.
| Warning | How long the pause is | When touring comes back |
|---|---|---|
| 1. | 5 minutes | when the counter runs out |
| 2. | 10 minutes | when the counter runs out |
| 3. | indefinite — account blocked | only an administrator lifts it |
Three things worth knowing:
- The first suspicion blocks nothing. All you get then is the message Something looks off — the warning is counted only when the position looks suspicious again.
- How to lift the pause: turn off the app that swaps your position (and the test provider in developer options), then tap Check again on the lock screen. The pause passes on its own anyway — the counter shows how much is left.
- No internet does not lift the pause. The report of the event then waits to be sent, and the pause holds until the server confirms it.
What never to send us#
- passwords to your account or its hint,
- a card number, a CVC code or a BLIK code — there are no payments in the app, and tokens are a closed currency that you cannot buy for money (Rewards and badges),
- verification codes from an SMS or from an e-mail,
- photos of an ID, scans of documents or personal data belonging to other people.
We never ask for these — not in the app, not in a message, not through anyone who claims to be Fyndi. An error report contains only technical data: the app version, the time, the phone model and the beginning of the stack trace.
Documented for app version 0.120.1 (updated 2026-09-26).
Machine translation — the Polish version prevails.