-
Notifications
You must be signed in to change notification settings - Fork 30
How To: Export Logs From The App
If you have been asked for a log, or you are about to report a problem, this is how to get one.
The button is hidden by default, because most people never need it. Turning it on takes two taps.
Before exporting, not after. The log keeps only the last 500 lines, so anything older has already scrolled away. If the app crashed, reopen it and do the thing that crashed it again.
Settings → Enable debug data, then back on the map open the ⋮ menu in the top right → Export Logs, and choose where to save it.
| Settings → Enable debug data | Map ⋮ → Export Logs |
|---|---|
![]() |
![]() |
Nothing is removed from this file. It is a raw Android log, and it can contain your Apple ID, your device names, tag names, serial numbers, and anything a notification happened to say while it was recording.
Open it, skim it, and take out anything you would not put on a public page. Nothing anybody needs in order to help you requires those.
Warning
Never paste your Apple ID password, a verification code, or a device passcode. No answer to any problem requires them, and none of them belong in a log in the first place.
👉 Report a problem with the app
The form asks for a few other things — your app version, your phone, and what you were doing. All of it helps, and the log helps most.
Enable debug data is not only about logs. With it on, the app also shows the underlying values on a tag's own screen and in its location history — beacon and naming-record identifiers, the raw model and product ids, pairing dates, battery readings.
Useful when a tag is behaving oddly and you are trying to describe which tag and what it claims to be. Harmless to leave on, and easy to forget about — turning it back off afterwards is only a matter of taste.
It is the Android system log (logcat), filtered to this app and trimmed to its last 500 lines. It
is not written continuously to a file, which is why exporting it after restarting the app usually
produces nothing useful — the interesting part is gone.
If your problem is with the exporter on a computer rather than the app, its log comes from a different place, and the window's Save logs… button takes the obvious identifiers out for you before writing the file.
🆘 In cases of issues or bugs, feel free to open an Issue on this page with logs from the app

