Trackhop
Reporting a problem
- Reproduce it once if you can, so the log is fresh.
- Settings → Diagnostics → Report an issue: it opens a new GitHub issue with the diagnostic report already filled in. Read it, remove anything you prefer not to share, add one or two sentences on what you were doing, and send it.
- No GitHub account? Developer options → Share diagnostics gives the same report as text.
The report contains the app and Android version, which connectors are connected (never tokens or passwords), the syncs with their source and target services, the last runs with counts, and the last log lines. Track and playlist names may appear in the log: remove them if you like.
What makes a report useful:
- what you expected, and what happened instead;
- the sync involved and the time it ran (the log is in chronological order);
- for a wrong match: the source track, the track that was picked, and the right one if you know it.
Security issues: see SECURITY.md, not a public issue.