Skip to main content

​
The fast way — TestFlight

Best for anything you can see on screen.
1

Screenshot the problem

Side button and volume-up together.
2

Tap the preview in the bottom-left corner

Within a couple of seconds, before it disappears.
3

Share → TestFlight

4

Write a sentence, send

TestFlight attaches your app version, iOS version, device model and diagnostics automatically — which saves the exchange of emails that usually starts every bug report. Full detail: Sending feedback from TestFlight.

​
The other way — the feedback site

Menu → Feedbacks & Bug reports, or feedback.vitalitytracker.app. Better for longer thoughts, things that are not a single screen, or ideas rather than faults. Other testers can see your post and add to it, which turns one report into several. It has its own sign-in and its own invitation email — see The feedback site.

​
What makes a report useful

You do not have to write a report. A sentence and a screenshot is genuinely enough. If you have the energy, three things help most:
  1. What you expected — “I expected a sleep score for last night”
  2. What you got — “it showed a dash”
  3. Anything unusual about that day — travelled, forgot the ring, watch died, changed a setting
The third one solves more bugs than the other two combined. A surprising number of apparent faults turn out to be the app correctly reporting a genuine gap — and only you know your Tuesday was unusual.

​
Always worth including

The build number. Bottom of the side menu, also shown in TestFlight. We ship often. Knowing which build you are on tells us exactly which changes could be responsible, and frequently answers the question before we look.

​
What happens next

We read everything. You may not get a reply to each one — a report that confirms something we already know is still useful and may not need an answer. If we need more from you, we will ask.

​
Not sure if it is a bug?

Report it anyway. A duplicate costs us seconds. A real fault nobody mentioned because they assumed it was known can survive to launch. The one exception is the known-inert list, which is genuinely already known.