A good bug report is not a long one. It is a specific one. Six lines beats six paragraphs.
Please include
What you did — the exact steps, in order. "Uploaded a card, then opened Daily for
15 August" is a report; "the charts don't work" is not.
What you expected, and what happened instead.
Where — New Look or Legacy, web or the Android app, and which browser.
When — date and rough time, and your time zone. It is how we find the matching
server-side record.
Which machine the data came from — make and model. A surprising number of bugs are
vendor-specific.
Whether it repeats. Once, every time, or only after a particular step?
Screenshots help — clean them first. Crop out your name, profile name, email address
and the device serial number. See the screenshot topic in Data Talk.
Please do not post here
Your account email, password, or anything that identifies your account. If we need it,
we will ask for it privately.
Somebody else's data.
Billing disputes and "my subscription is wrong" — those need your account looked at,
which means the in-app feedback button, not a public thread.
What happens next
Reproducible reports get investigated and answered in the thread. Reports we cannot
reproduce get questions — please answer them, because that is usually where the real
trigger turns up. A confirmed fix is announced in Announcements & Updates with the
version it shipped in.
One report per thread, please. Two bugs in one thread means one of them gets forgotten.
Nothing on SomniTalk is medical advice. Talk to your own clinician before changing therapy.
