Skip to main content
TestFlight has feedback built in, and it is the best way to tell us something is wrong. It takes about twenty seconds and it attaches things we would otherwise have to ask you for.

​
The screenshot method

1

Take a screenshot when you see the problem

Press the side button and volume-up together.
2

Tap the little preview in the bottom-left corner

Before it disappears — you have a couple of seconds.
3

Tap Share, then choose TestFlight

4

Type what happened, and send

One sentence is plenty. “Capacity says Needs HRV but my Oura synced this morning” is a perfect bug report.

​
What gets sent with it

Along with your screenshot and your note, TestFlight attaches the app version, your iOS version, your device model, and basic diagnostics. That saves an exchange of emails asking which build you are on — which is usually the first thing we need to know.
It does not send your health data. It sends the screenshot you chose to take and technical details about the app and phone.

​
The other way in

You can also open TestFlight, tap VT Workbench, then Send Beta Feedback without a screenshot. Useful for “this is confusing” rather than “this is broken”.

​
What makes a report useful

You do not need to write a report. A sentence and a screenshot is genuinely enough. But if you have the energy, these three things help most:
  1. What you expected — “I expected a sleep score”
  2. What you got — “it showed a dash”
  3. Anything unusual about that day — travelled, forgot the ring, watch died
The third one solves more bugs than the first two, because a surprising number of “faults” turn out to be the app correctly reporting a genuine gap.

Other ways to reach us

The feedback portal, and what not to report.