FlutterFlow generates AAB with Version Code 16 even after changing Build Number to 18

[rpatidar7697-netizen]

Can we access your project?

• I give permission for members of the FlutterFlow team to access and test my project for the sole purpose of investigating this issue.

Current Behavior

I changed the Build Number (Version Code) from 16 to 18 in App Settings > Mobile Deployment.

The project is synced successfully.

I generated a new AAB multiple times.

However, Google Play Console always reports:

"Version code 16 has already been used. Try another version code."

It appears FlutterFlow is still generating an AAB with Version Code 16 instead of 18.

Please investigate this issue.

Expected Behavior

A newly generated AAB should use Version Code 18 instead of Version Code 16.

Steps to Reproduce

1. Open App Settings > Mobile Deployment.
2. Change Build Number from 16 to 18.
3. Save and Sync the project.
4. Generate a new Android AAB.
5. Upload it to Google Play Console.
6. Google Play Console still detects Version Code 16.

Reproducible from Blank

• The steps to reproduce above start from a blank project.

Bug Report Code (Required)

IT4wkvLqw4tOoctF7arcdcFVmiURMjskapEale1hQis8JJToPLAUZ8zBM05vZr3hTAhifVmGin8y/Pfqv9/LMPdfNTucQN1IybtpEDzdfD26eJiDPZe/fW1TN/xRf0CMy6ujkRJDHNRvSHA93GGqO+vKfALBNpCwPlYROMiLKdeK2SrDX1iXc2URm05KZDPz

Visual documentation

Screenshots attached.

Screenshot 1: FlutterFlow Mobile Deployment showing Build Number = 18.

Screenshot 2: Google Play Console showing the error:
"Version code 16 has already been used. Try another version code."

These screenshots demonstrate that FlutterFlow is generating an AAB with the old version code instead of the updated version code.

Environment

FlutterFlow version: Latest
Platform: Web
Browser: Google Chrome
Operating System: Windows 11

Additional Information

This issue prevents me from publishing updates to Google Play because every generated AAB still contains Version Code 16.