Bug reports
⚠
The app sends no automatic crash reports. No telemetry is collected. If you do not tell us about a bug, nobody finds out about it.
The in-app error log
Since 0.2.3 the app keeps its own error log on the device. You will find it under Settings → Diagnostics:
- View — the list of captured errors with timestamps
- Save to file — exports the log as a text file
- Clear — empties the log
A repeating error is written three times and then dropped, so one problem cannot flood the whole log.
ℹ
The log never leaves your device. It sits there and you decide whether to send it. When reporting a crash, attach it — it saves a lot of guesswork.
Where to report
| Channel | When to use it |
|---|---|
| Web form — beta program page | The standard route. It has prepared fields so you do not forget anything. |
| Discord | When you are not sure whether it is a bug, or want quick advice. |
| Email — [email protected] | When you need to attach a file — the error log, a backup or a problematic import. |
What belongs in a report
Always
| Detail | Where to find it |
|---|---|
| App version | Settings → About (version number and build) |
| Platform and OS version | Android 14, iOS 17, Windows 11… |
| Device model | Especially for less common phones and tablets |
| What you did | The steps that led to the bug, one by one |
| What you expected | How you thought it should behave |
| What happened | What happened instead |
When you can
- The error log from Settings → Diagnostics → Save to file — for crashes this is the single most useful attachment
- A screenshot or a short video — for visual bugs it saves half an hour of writing
- The exact error message — sync error states are named, so the message tells us where it broke
- The file that caused it — for import bugs this is practically a requirement
- Whether it repeats — every time, or only sometimes?
Sync bugs
Sync is the most complex part of the app and also the one that depends most on the environment. For sync problems, add:
- Both devices — platform, OS version and app version for leader and member alike
- Network type — home WiFi, phone hotspot, venue network, public WiFi
- Your role — was your device the leader or a member?
- Which stage failed — not discovered, did not connect, connected then dropped, or data did not transfer?
- The error message verbatim
Before reporting, please go through the mDNS troubleshooting section — a large share of network trouble can be fixed on the spot and it saves both sides time.
Example of a good report
text
Version: 0.2.7 (build 10)
Device: Samsung Galaxy Tab A8, Android 13
Role: member
Steps:
1. Leader (iPhone 13, iOS 17) started a session on home WiFi
2. I scanned the QR code on the tablet
3. It connected, I could see the member list
4. The leader changed song
Expected: switch to the same song
Happened: the tablet stayed on the old song, after ~20 s the
message "Leader disconnected" appeared
Repeats: every time the tablet has been in the session for more
than 2 minutes. Did not happen on a different WiFi.
A report like this can be acted on without further questions — it has the version, both devices, the network, reproduction steps and an observation that narrows the bug down.
What happens to a report
A report submitted through the form goes into an internal processing queue. Bugs are prioritised in this order:
- Data loss — anything that deletes or corrupts a library
- A crash or a state with no way out
- Sync not working on an ordinary network
- A broken main scenario — import, export, stage mode
- Cosmetic and minor issues
What happens to the submitted details from a privacy standpoint is described in the Privacy policy.