Help us make InVivo dependable.
TestFlight is the official support and feedback channel for this preview. A short, reproducible report is enough; you never need to send health records or raw sensor data.
feedback stays tied to the beta build
path, expected, actual, repeatability
health details are not needed for triage
individual responses are not guaranteed
Send feedback through TestFlight
- Open the TestFlight app and choose InVivo from your Apps list.
- Tap “Send Beta Feedback,” then choose “Include Screenshot” or “Don’t Include Screenshot.”
- Add a brief description, review the attachment, then tap “Submit.”
Mark up the screen that went wrong
While InVivo is open, take a screenshot, tap its thumbnail, then choose Done and “Share Beta Feedback.” Crop or cover anything private before submitting it.
TestFlight supplies app version, build, device, and operating-system context with feedback. Focus your note on what you did and what you saw.
Four facts turn a rough edge into a reproducible issue.
Please do not keep retrying anything that feels unsafe or appears to damage data. One clear report is more useful than forcing the failure again.
Where you were
Name the tab or screen and list the taps that led there. A short path such as “Today → feature card → Start” is ideal.
What you expected
Describe the result you thought the action would produce in one sentence.
What happened
Describe the visible result, including any plain-language error shown by InVivo. Avoid copying private health content.
Can it repeat?
Tell us whether it happened once, every time, or only after a particular permission or optional device was involved.
Describe the behavior, not your biology.
Screenshots and comments are shared through TestFlight. Review both before submitting and include only what the team needs to reproduce the product issue.
Safe and useful
Leave private details out
Do not attach health records, lab values, medication details, journal text, raw signals, faces, addresses, account identifiers, or unrelated notifications. Crop, blur, or omit a screenshot if it reveals any of these.
The beta remains your data and your decision.
Testing never requires you to connect a health source, grant an optional permission, or keep local data you no longer want.
Delete local InVivo data
In the app, open Profile → Data & Privacy → Delete all data. Read the confirmation before continuing. Data owned by Apple Health or another connected service remains governed by that service's controls.
Wellness preview, not medical care
InVivo is not a medical device and does not diagnose, treat, or provide emergency care. Do not use beta feedback to seek medical advice. For an urgent medical concern, contact a qualified clinician or local emergency services instead of waiting for a beta response.
TestFlight is the contact route for this beta.
Reports submitted in TestFlight reach the beta team with the relevant build context. This page has no form and does not collect messages, and no separate public support inbox is published here.
We review beta feedback, but an individual reply or a particular response time cannot be guaranteed during the preview. If an invitation or installation problem prevents you from reaching TestFlight feedback, reply through the same channel that delivered your invitation. Never send urgent health questions or private health records through that channel.