GuideTrustiPhoneMac
Report a bug
Shake the phone, tap Report a bug in the menu or sidebar, or open Help and feedback. Say what you expected and what happened. Here is what travels with the report and what never does.
You are one of a hundred people using Kept before anyone else. When something is wrong, a report from you is the fastest way it gets fixed. Reports go to a private inbox that a person and our triage agents read every day.
Send one
- iPhone. Shake the phone, including while typing in a note or child page. A short sheet asks Report a problem?; tap Report and a screenshot of the screen you were on rides along. Or tap your avatar and choose Report a bug at the very bottom of the menu, under Settings: the menu closes, and the report opens with a screenshot of the screen you were on, never of the menu. Or go to Settings → Help & feedback → Report a problem; from Settings no screenshot is attached, so add one if you have it.
- Mac. Click Report a bug at the foot of the sidebar, beside the Settings gear, or go to Settings → Help & feedback → Report a problem. Both open the same report and note which screen you were on. Attach an image by dragging it in, choosing a file, or pasting.
Write what went wrong, pick the closest kind, Wrong data, Sync, Frozen, Layout, AI result, or Other, and, if you like, what you expected instead. A sentence like I checked the second habit on Today and the ring did not move is worth more than a paragraph about the app being off.
Up to four screenshots or a short video can ride along. Look at every pixel first: a screenshot can show a note title or a task name that the rest of the report never would. Remove screenshot if you would rather not. If the phone is offline, the report waits in Settings with a Try now and sends itself when you are back.
While Shake to report is on, use the editor’s Undo control to undo typing. After you close a report or dismiss its confirmation, the parent link at the top of a child page remains available. During Capture, the meal camera, or when Kept is inactive, shake keeps its system behavior. Repeated shakes while a report is open, or during the short pause after dismissing it, do not open another prompt or Undo Typing. Turning Shake to report off restores the system shake-to-undo gesture.
What travels with the report
| Always | Never |
|---|---|
| Your description, category, and the screen you were on | Note bodies or capture text |
| App version, build, OS, device | Health details or meal contents |
| Time since the device restarted and free storage | |
| Locale, time zone, network state | Authentication tokens |
| Which modules and rollout switches are on | Request or response bodies |
| How many changes were waiting to sync | Raw URLs |
| Accessibility, thermal, and low-power flags | Anything from another account |
The pack is versioned so a reviewer can trust exactly what is in it.
The optional activity trail
Include recent activity trail, off by default, adds the names and times of the last fifty app events: task_completed, capture_committed, that kind of thing. No content, ever. It helps enormously with bugs that involve timing. Leave it off if you prefer. If Kept crashed recently, the crash record, where the code stopped and never anything you wrote, is included without asking.
Shaking is on by default and off in Settings → Shake to report. Turning it off leaves Report a bug in the menu and sidebar exactly where it is. Show feedback button adds a small always-on button at the edge of the screen for people who would rather tap than shake.
What happens next
A reviewer reads the screenshot first, checks whether the report matches one already open or a bug already fixed, and separates defects from wishes. Fixes ship in the next build, and we close a report only once the fix has been verified on the build it rides in. Wishes go to a product list where they wait for enough people to want them.
Reports and feedback never affect a Founding Practice benefit. Sending one, or never sending one, changes nothing about what your account was promised.