If the FAQ and the rest of this section didn't solve it, here's how to get a real answer from the team.
Reach out through your invite channel
Squabble is currently invite-only, so the fastest way to reach us is through whichever channel got you your invite or beta access in the first place — reply there with what you're seeing. Include your guild name and the book involved if the issue is guild- or playback-specific; it helps us reproduce it faster.
Export your diagnostic logs first
Before you reach out, exporting a diagnostics log gives the team far more to work with than a description alone. Squabble's Diagnostics section in Settings captures activity in memory — nothing is collected unless you turn it on.
Open Settings and enable logging
Scroll to the Diagnostics section and turn on Enable Logging. It's off by default and doesn't run unless you flip it on.
Turn on the categories that match your issue
Options include Firebase calls, Battery / player, Comment reveals, Progress sync, and UI load times. Enable whichever relates to what you're seeing — enable more than one if you're not sure.
Reproduce the problem
Tap Start Capture, do the thing that triggers the issue, then tap Stop Capture.
Export and share
Tap Export Logs to open the share sheet, then send the exported file along with your report.
What to include
- What you expected to happen, and what happened instead
- The guild, book, or screen involved, if relevant
- Your device type and OS version
- The exported log file from the steps above