How to send Google Play beta feedback and find it in Play Console

To send feedback for a closed or open Google Play beta, open the app's page from the Play Store's Beta list and use Private feedback to developer. Developers read those submissions in Testing feedback in Play Console. For an internal test, give testers a direct reporting channel in the invitation.

This guide covers feedback about an app distributed through Google Play. Google's Android Beta Feedback app serves the Android operating system's beta and developer previews. Send an app's beta observations through the route its developer provides.

How do testers send private feedback from the Play Store?

For a closed or open beta, follow Google's tester feedback instructions:

1. Open the Play Store and tap your profile icon.
2. Select Manage apps and devices, then Beta.
3. Open the app's details page.
4. Under Private feedback to developer, choose Write feedback.
5. Select a star rating and describe the issue. Google requires both before submission.
6. Tap Post.

Google describes this feedback as visible only to the developer. Keep the description focused on one observation so the person reading it can ask a useful follow-up question.

Where do developers find beta feedback in Play Console?

Select your app in Play Console, then open Ratings and reviews → Testing feedback. You can search the text, filter by criteria such as app version or device, and reply to testers. Google's guide to reviewing testing feedback documents this view separately from production reviews.

Check the selected app and filters before concluding that a report is missing. Also check where the tester submitted it: an email or a form response belongs to that channel's inbox. Reviewing Play Console alone does not cover every route mentioned in your beta invitation.

Which feedback route should each testing track use?

Google's testing-track guide documents private Play feedback for closed and open tests. It also lets developers provide a feedback URL or email address on the tester opt-in page. Feedback from test users does not affect the app's public rating.

Testing track	Route to put in the invitation	Where the team reviews it
Internal	A direct feedback URL or email address	The supplied channel
Closed	Private Play feedback, with a direct channel for supporting evidence	Play Console and the supplied evidence channel
Open	Private Play feedback, with a direct channel for supporting evidence	Play Console and the supplied evidence channel

Choose a default for specific defects and say who reads it. For example: “Report a failed task through the beta issue form; include the build and a screenshot if it helps.” A tester should be able to find that instruction again without searching an old chat thread.

What should testers write when they find a bug?

Describe the failed task, the starting state and the difference between the expected and actual result. Add the installed app version and build when available, plus the device and Android version. State what you observed about frequency rather than guessing how many people are affected.

Here is a fictional report for a delivery app. It is an example of useful content for a feedback message or the team's issue form:

Summary: Delivery note disappears after returning from the camera
Build: 2.8.0 (142), closed test
Device: Pixel 8, Android 16

Starting state: Signed in with the supplied test account; one delivery open.
Steps:
1. Enter a delivery note without submitting the delivery.
2. Open the photo capture screen and take a photo.
3. Return to the delivery form.

Expected: The note remains alongside the new photo.
Actual: The photo is present, but the note field is empty.
Frequency: Happened twice in two attempts on this build.
Impact: I have to retype the note before completing the delivery.
Evidence: Screenshots before opening the camera and after returning.

Use test data and remove private details from any images before sharing them. If the reporting route does not offer the attachment you need, use the team's agreed evidence channel and include enough context to connect the evidence to the original message.

The beta issue template gives testers a reusable structure. For the reviewer, the bug intake triage worksheet helps turn that observation into an investigation, an owner and a next action.

What should you check if the beta app or feedback option is missing?

First confirm the Google account used for the test invitation and whether the tester has completed the opt-in process. For a closed test using a Google Group, Google requires joining the group before opting in. An internal or closed app may also need a direct store link rather than a search. These access rules are documented in Google's instructions for sharing a test.

Then confirm which testing track the organiser intended. For internal testing, return to the supplied feedback link or email address. If the invitation has no reporting instructions, ask the organiser for them before spending time looking for a private Play feedback form.

Record the installed build with the report. The label “beta” is not enough to identify the code that produced an observation, especially when a tester has participated in several test rounds.

How do you turn Play beta feedback into an engineering issue?

Keep the tester's description beside the engineering issue and record what you'll check next. Ask for a missing condition explicitly: “Did you upgrade from the previous test build?” is easier to answer than “Can you send more details?” Reply through the original channel so the tester knows the report has reached someone.

If testers need to send reports from inside the app, the BugScreen Google Play workflow works with builds distributed through Play's testing tracks. The embedded Android SDK attaches app version, version code, device and OS context to reports; see the collected-data guide. The companion app provides a route for screenshots and tester-entered details when you cannot change the beta build. It cannot read the tested app's logs or build metadata.

To set up in-app reporting for your next Android test round, create a BugScreen account and follow the Android SDK setup guide.