Google Play rejects Adalo Responsive Android build due to versionCode already used

[Yuki.O]

Google Play is rejecting our new Android AAB with “version code already used.”
For the same package name, the latest bundle already uploaded to Play Console has versionCode 329, so any new build must be 330+.

In the Adalo Responsive builder, I can’t find any way to manually set or increase the Android versionCode. Each new build still results in a lower versionCode and gets rejected by Play Console.

I don’t want to change the package name or create a new app.
How can I force the next Responsive Android build to use a versionCode higher than 329?

Originally, I created a Responsive app by copying from the Legacy app and built it around 7 times.
I then deleted that Responsive app entirely.
After that, I created a new Responsive app again by copying from the same Legacy app.

Even though the previous Responsive app was deleted, it seems the versionCode increments from those builds are still being counted for the same package name, which is causing the current versionCode conflict.

[Dilon]

https://help.adalo.com/testing-your-app/publishing-to-the-google-play-store/troubleshooting-android-release/error-version-code-xxx-has-already-been-used.-try-another-version-code.

[Ali-Bazzi]

Hey @Yuki.O, what is the version number of your latest build that was submitted and rejected?

[Ali-Bazzi]

@Yuki.O, quick add from experience: this error persists extra often when the responsive app was copied from a legacy one (even after deletion), since Google Play ties the highest code (329) to the package name forever.

Follow the guide Dilon shared: discard release => check highest version code in Releases Overview => submit ticket to Adalo support with project URL, screenshots, and description => responsive copy history.

They increase the base version code => next build increments properly. Usually 1–2 days. Don’t rebuild in the meantime.

Let us know when sorted!