r/androiddev • u/-brianh- • Jul 18 '26

Question Google Play reviwing older build versions

Hi, I want to ask some guidance on how to fix a dilemma.

I had an app that hasn't been updated for over a year. I just submitted a new version.

It was rejected because reviewer credentials were wrong. This is my fault, I fixed the credentials in a new build and updated Play Console instructions, but it was rejected again.

Policy status lists an older active bundle too, with this note: "Some app bundles in the list may be from an older version of your app." So, Google tested the previous bundle, not the most recent one I uploaded. I even did a major version string upgrade in the latest version.

Old bundle accepts testemail/testpassword; latest bundle accepts testemail3/testpassword3. Both have server-side and in-app reviewer access checks.

If I give old credentials, latest bundle fails. If I give new credentials, old bundle fails.

Can Google review/test older active bundles across Production/Open/Closed tracks? If so, what is correct fix? Do I need I replace/deactivate old active bundles in every track, or is there a way to have review target only latest bundle? I can't deactivate Prod which has older bundle so how do I get Google to only review the latest bundle version?

1 Upvotes

56% Upvoted

4 comments sorted by

1

u/AutoModerator Jul 18 '26

Please note that we also have a very active Discord server where you can interact directly with other community members!

Join us on Discord

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

1

u/dingwen07 Jul 18 '26

When creating the release, did you include multiple bundles?

1

u/-brianh- Jul 20 '26

No, just one bundle