Tester feedback
Every install page has a Send feedback button under the install buttons. Testers use it to report a bug, confirm a build works, or suggest a change, with up to three screenshots. Nothing to install, no account to create. Available on every plan.
What a tester sees
- Open the install link (or scan the QR code) and tap Send feedback.
- Pick a kind: Bug, Works, or Suggestion.
- Add a name, an email, and a message. On a page that shows both iOS and Android, pick which build the feedback is about.
- Optionally attach screenshots (PNG, JPEG, WebP or GIF, up to 5 MB each, up to three).
- Tap Send feedback.
The name and email are remembered on that device, so the second message takes a few seconds.
Where it lands
- Feedback page: every project has a Feedback entry in its sidebar, with an open count. Filter by status and kind, search by message, name or email, and open screenshots full size.
- Build page: each build shows its own feedback under the share links, and the builds list shows an open-feedback count next to the build.
- Email: the person who uploaded the build gets an email for every message, with the text and a link to the build. If the uploader no longer exists, everyone in the organization gets it.
Mark feedback Resolved when it is handled; reopen it if it comes back. Deleting feedback also deletes its screenshots.
Limits
- 2000 characters per message.
- 10 messages per hour from one device per project, and 500 per build. Testers who hit the limit see a plain message asking them to try later.
- Screenshots count toward the project's storage plan. When storage is full, the message still sends without them.
Reading it from an AI agent
The buildtree MCP server exposes the same list, so a coding agent can pull the open bugs for a build and start on them. See AI agents.
Related
Last updated