-
Notifications
You must be signed in to change notification settings - Fork 0
Reporting a bug
Open More, tap Feedback & Bug Reports, then File on GitHub.
The app shows you a short summary of your setup first, and opens the bug form with it already filled in. The summary holds your build, your iOS version, your device, whether the app's online, how many changes are waiting to sync, and how many files you've downloaded. It classifies your server, for example "signed in (https, Tailscale)". It never includes your server's name or address.
Nothing's sent until you tap.
Reading something when it happened? The reader's menu has a round bug button that opens the same report with the book and your position already filled in, ready to screenshot or file. TestFlight builds only.
Share Logs on that screen saves the app's own log lines from the last fifteen minutes as a text file, with your server's host name blanked out. Attach it if I ask for it.
Please include:
- What you did. Step by step, from opening the app.
- What you expected.
- What happened instead.
- Which book, and what kind: audiobook, EPUB, PDF, comic.
Steps I can follow are worth more than everything else combined. A bug I can repeat is a bug I can fix.
Use TestFlight's Share Beta Feedback. Take a screenshot, shake the phone or open TestFlight, and send it. The screenshot goes with the report, which a GitHub issue can't do as easily.
Start a Q&A discussion. I'll open an issue if it turns out to be one.
I copy the report into my private repo and work on it there. That cross-reference is invisible to you, so I comment here too: tracked when I've picked it up, needs-info if I'm stuck without more from you.
When the fix reaches TestFlight I'll comment with the build number and close the issue. Update in TestFlight, try it, and reopen the issue if it's still there.