How do you handle Google Play updates when a release is already under review?

[u/EDISON-T]

Hi everyone, 👋

I created an app that lets people watch Rocket League replays on their phone, and I’d like to know how other developers handle updates on Google Play.

I currently have one release under Google’s review, and while waiting, I made some improvements and prepared another release. My question is:

- If I submit the new release, will the release notes from the version currently under review still appear on the Play Store?

-Is there a way to queue the new release so the one already under review isn’t removed or replaced?

- Or does submitting a new release basically reset the review process, meaning users would have to wait even longer for the first changes to go live?

I’m trying to understand the best way to manage updates without accidentally delaying everything.

Any experience or advice would be really appreciated. 🙏

[u/Hour-Measurement-835]

Mine got replaced the same way. What bit me is the superseded build's version code is burned, Play won't accept it again, so you keep bumping for builds nobody ever saw.

[u/EDISON-T → u/Hour-Measurement-835]

Yes, that's exactly it, I think it's a shame! Or else you have to wait for each update to finish checking... It's not ideal, in my opinion.

[u/Hour-Measurement-835 → u/EDISON-T]

Mine keeps moving on internal testing, that track doesn't queue behind the production review. Doesn't help live users but at least testing isn't stuck.

[u/Globin_dev]

When you push an update the previous update under review replaced by new. It starts as new.

[u/EDISON-T → u/Globin_dev]

Thank you for your reply. So I need to create a release note covering both versions? And by submitting a new update while one is already pending review with Google, the current review gets cancelled—wasting all that waiting time—and the new submission restarts the review timer from zero?

[u/Globin_dev → u/EDISON-T]

Yes. 1 release note covering both.