Bug reports
⚠
The app sends no automatic crash reports and collects no telemetry. If you do not tell us about a bug, nobody finds out about it — but there is a button for telling us, right inside the app.
Reporting from the app
The shortest route is Settings → Help and privacy → Report a problem. You write what
went wrong, optionally how to reproduce it, and send.
The app fills in the version, the operating system and the device model itself, so you do
not have to look them up and copy them out. What exactly the report contains is shown
in a preview before you send it:
| Part of the report | Default |
|---|---|
| Your description, a report number, the app version and the OS | always |
| Device and display details — manufacturer, model, system version, resolution, text scaling | on, can be turned off |
| Technical diagnostics — a cleaned error log | off |
| An email address for a reply | optional |
| A screenshot | optional, you pick it yourself |
Your songs, libraries, notes and attachments never end up in a report.
Instead of sending, you can tap Open email — the app opens your mail app with a
prefilled message, so you send it yourself and see exactly what goes out.
ℹ
When you want to attach a file to a report — a backup, or the import it crashes on — go the email route. A screenshot can be attached when sending directly; other files cannot.
The in-app error log
The app keeps its own error log on the device. You will find it under Settings → Help and privacy → Error log:
- 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 on its own. It sits there, and it is attached to a report only when you tick it while sending. When reporting a crash, attach it — it saves a lot of guesswork.
Where to report
| Channel | When to use it |
|---|---|
| From the app — Settings → Help and privacy → Report a problem | The shortest route for a bug in the app. It fills in the version and the device. |
| Web form — beta program page | When the phone is not in your hand, or the bug is on the website. 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 — a backup or a problematic import. |
What belongs in a report
Always
When you report from the app, the first three rows are filled in for you and the last three are yours.
| Detail | Where to find it |
|---|---|
| App version | Filled in for you; by hand in Settings → About |
| Platform and OS version | Filled in for you (Android 14, iOS 17, Windows 11…) |
| Device model | Filled in for you unless you turn device details off |
| 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 — in a report from the app you include it by ticking technical diagnostics, or export it from Settings → Help and privacy → Error log → 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 network 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.4.1 (build 19)
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.