Yes, Google Play now shows submission history

Does Google Play now show submission history in Play Console

Yes. Google Play now shows submission activity in Play Console, and the page records each submission’s status, timestamp, source, and submission ID. Google says the records are displayed starting May 1, 2026, with up to one year of history from that point forward.

The page name in Google’s help center is “About your submission activity.” That matters because people often look for a generic “history” tab and assume the feature is missing. Google describes it as a place to view and monitor publishing activity, not just a passive log.

The practical change is that each group of changes now becomes a unique submission. In the submission activity page, you can open a record and see what was included, when Google received it, how it was submitted, and what state it reached. Google also says the page includes a submission ID you can use when asking support for help.

People get one part wrong: submission activity is not the same thing as the Activity log. The Activity log shows changes made in Play Console by account users over the lifetime of the developer account, while submission activity tracks publishing submissions and their review states. If you want who changed a setting, use Activity log. If you want what happened to a release, use submission activity.

The new view also makes the release lifecycle easier to read. Google lists the states In review, Ready to publish, Published, Rejected, and Cancelled. The “Cancelled” state can appear when you withdraw the changes, when a newer submission supersedes an older one, or when the app is blocked or suspended. That is useful when a release disappears and you need to explain why.

The inconvenient part is the retention window. Google says it will maintain up to one year of submission history from May 1, 2026 onward. That means this is history, but not full archive retention. Older release work still needs your own records if you want to keep a long trail outside Play Console.

If you are trying to confirm whether a specific update reached review, the submission activity page is the first place to check. Open the submission, then look at the status update timestamps and the source field. Google says the source shows whether the submission came from the Play Console interface or the Publishing API. That can matter when a team uses both.

If a submission is rejected, Google says the latest rejected submissions include a link to the Policy status page, where you can see details of the issue and instructions for fixing it. That is the part people usually want after a failed launch, because it connects the record to the reason the update stopped.

For developers who are still getting production access through closed testing, this history is useful but separate from the testing requirement. Google’s current help center says personal accounts created after November 13, 2023 must have 12 testers opted in continuously for 14 days before applying for production access. Submission history does not replace that requirement, it only helps you track what you submitted and when.

A simple way to use the new page is this: submit a release, wait for review, then open submission activity and verify the exact state transitions. If you are debugging a release that was withdrawn or replaced, compare the submission ID and the timestamp against the release you expected to be live. That is the cleanest way to prove what happened without guessing.

If you need a related place to keep your own release notes, testing links, and launch checklist, DevConnect is separate from Play Console and stays free to use at https://devconnectplatform.com. Google’s submission activity page is still the source for review history inside Play Console.

The short answer is yes, Google Play now shows submission history in Play Console. The longer answer is that it is a submission activity page, it starts from May 1, 2026, and it keeps up to one year of records, not a forever archive.

FAQ

Is submission activity the same as release history No. Submission activity tracks the review record for each submission, while release pages track the app’s releases and rollouts. Use submission activity when you need to see review state changes, submission IDs, or the source of a submission.

Can I see who submitted the change Google says submission activity shows whether a submission came from the Play Console interface or the Publishing API. For account-user actions more broadly, the Activity log shows the email address of the user who made a change. Those are different records for different questions.

How far back does the new submission history go Google says it keeps up to one year of history starting May 1, 2026. Earlier records are not promised by the help center article, so teams that need a longer audit trail should save their own release notes and support records.

What should I check when a release never appeared Open the submission activity page and look at the status timeline. If the submission is Rejected, the policy link on the rejected record should explain the issue. If it is Cancelled, Google says a newer submission, a manual removal, a block, or a suspension may have replaced it.

Does this change the 12 tester rule for new personal accounts No. Google’s testing requirement for personal accounts created after November 13, 2023 is still a separate production-access rule. The submission history page does not reduce the tester count or the 14-day requirement.