Quick answer: Connect your app under Integrate > Integrations > Google Play with a Google Cloud service account that has the Reply to reviews permission in Play Console. Bugnet imports new reviews every hour with the device, Android version and app version, keeps a history beyond Google's seven-day window, lets you reply publicly from the dashboard, and, if you switch it on, files one- and two-star reviews that describe a bug (crashes, freezes, lost saves, black screens and so on) as bug reports linked to the review. It is available on every plan.
Mobile players rarely go looking for a bug report form. When your game crashes on their phone, they open the Play Store and leave one star. Those reviews are some of the most valuable bug reports you will ever get: they come with the device model, the Android version and the app version attached. They are also scattered, short-lived in Google's API, and easy to miss. This guide shows how to turn them into a triaged bug list automatically.
Why Play reviews belong in your bug tracker
- They are often the only report you get. Most players who hit a crash never contact you; some leave a review on the way out.
- They carry device context. Google provides the device, the Android version and the app version for reviews, which is exactly what you need to reproduce a device-specific bug.
- They disappear from the API. Google's reviews API only returns reviews with text from the last seven days. Older reviews stay visible in Play Console, but not to any tool that reads the API.
- Replies move ratings. A public reply saying the crash is fixed in the next update is one of the few ways to win back a one-star reviewer.
What the integration does
| Option | What happens |
|---|---|
| Import new reviews | Every hour, new reviews are imported with the rating, text, author, device, Android version and app version, and kept as a history in Bugnet. |
| File 1–2★ reviews that describe a bug as bug reports | Low-star reviews that mention things like crashes, freezes, black screens, lost or corrupted saves, connection problems, lag or “won't load” become bug reports, linked back to the review. |
| Reply | Reply to any review from Bugnet. Replies appear publicly on your store page, up to 350 characters. |
What a filed review looks like
A bug filed from a review gets a title such as Google Play review (1★): Crashes every time I open the shop, the full review text, and a note with the rating, the reviewer's name and the date. Its platform is set to Android, its game version to the app version from the review, and its OS and device fields to what Google reported. Bugnet infers the category from the text, and a one-star review about a crash is filed at high priority.
From there it is a normal bug: it lands in your list next to crashes and in-game reports, notifies your team by email, Discord, Slack or Teams, and can be filed into GitHub, Linear, Jira, ClickUp, Trello or Notion like anything else.
Setup
1. Create a service account in Google Cloud
In the Google Cloud console, enable the Google Play Android Developer API for a project, create a service account, and download a JSON key for it.
2. Give it access in Play Console
In Play Console > Users and permissions, invite the service account's email address, grant it access to your game, and give it the Reply to reviews permission.
3. Connect it in Bugnet
Create a free Bugnet project if you do not have one. Open Integrate > Integrations > Google Play, paste the whole JSON key and your app's package name (for example com.studio.game), choose which options to enable, and choose Connect. Use Check connection to confirm access, and Sync now any time you do not want to wait for the hourly import.
Pair it with the SDK for the full picture
Reviews tell you something went wrong; the SDK tells you why. Add the Bugnet SDK to the game itself (Unity, Godot, Unreal, GameMaker, Construct 3, Pygame or web; see the SDK docs) and crashes arrive with the stack trace, the last 100 log lines, a screenshot, and the device, OS, GPU and RAM. When a review says “crashes when I open the shop” and the dashboard shows a NullReferenceException in ShopController on the same version, you have both the symptom and the cause.
Give players a better door than the review box, too: a “Report a bug” button in your pause or settings menu, wired to the in-game widget, catches many of the problems that would otherwise become one-star reviews.
A weekly review workflow
- Check the filed reviews in your bug list. Where one describes a bug you already track, add a comment pointing to it and close the review's report.
- Reply to bug reviews from Bugnet once you know the cause: acknowledge it, and say when the fix ships.
- Resolve the bug when the fix is live, publish a changelog, and reply again pointing to the update.
- Watch the version. Crash-free sessions per build and your review trend should both recover after the fix.
Limits worth knowing
- Google only exposes reviews with text from the last seven days, so the import builds your history from the day you connect.
- Filed reviews count toward your plan's bug report limit. When the limit is reached, reviews are still imported but no longer filed. The free plan includes up to 100 reports; Studio includes 10,000 and Studio Plus is unlimited.
- Replies are limited to 350 characters, which is Google's limit.
Shipping on iOS too? The App Store connection works the same way; see turning App Store reviews into bug reports and the Google Play and App Store docs.
Frequently asked questions
Can I turn Google Play reviews into bug reports automatically?
Yes. With Bugnet's Google Play integration and its File 1-2 star reviews that describe a bug option on, low-star reviews that mention crashes, freezes, broken saves, black screens and similar problems become bug reports with the device, Android version and app version attached, linked back to the review.
Why does the Google Play API only show recent reviews?
Google's reviews API only returns reviews with text from the last seven days. Bugnet imports every hour and keeps the history, so reviews stay searchable after they drop out of the API.
What permissions does the service account need?
Enable the Google Play Android Developer API in Google Cloud, create a service account with a JSON key, then invite its email in Play Console under Users and permissions with access to your app and the Reply to reviews permission.
Can I reply to Google Play reviews from Bugnet?
Yes. Replies are posted publicly on your store page and can be up to 350 characters.
Is the Google Play integration free?
Yes. It is available on every Bugnet plan. Reviews filed as bug reports count toward your plan's bug report limit.
A one-star review is a bug report with a bad attitude. Read it like one, fix it like one, and reply like a human.