AAB Download Always Returns Same Version Code (versionCode=3)

[kineticbursa-creator]

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

Hi FlutterFlow Support,

I'm experiencing a bug with the Android AAB build system. Every time I download an AAB file, it always contains the same version code (3) and version name (1.0.3), regardless of what I set in the Build Number and App Version fields in the Mobile Deployment settings.

Steps to reproduce:

1. Go to Mobile Deployment settings
2. Change Build Number (e.g., 4, 5, 6, 7, 8)
3. Change App Version (e.g., 2.6.1, 2.6.2)
4. Click Deploy to Play Store → wait for Success
5. Download AAB
6. The downloaded AAB always has versionCode=3 and versionName=1.0.3

This makes it impossible to upload new builds to Google Play Store, which rejects the file with error: "Version code has already been used."

Project ID: hidrolik-hesap-tqxcx1

Please help resolve this issue.

Thank you.

Expected Behavior

Each new build should have a unique version code matching the Build Number set in FlutterFlow Mobile Deployment settings.

Steps to Reproduce

1. Go to Mobile Deployment settings
2. Change Build Number (e.g., 4, 5, 6, 7, 8)
3. Change App Version (e.g., 2.6.1, 2.6.2)
4. Click Deploy to Play Store → wait for Success
5. Download AAB
6. The downloaded AAB always has versionCode=3 and versionName=1.0.3

Reproducible from Blank

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

Bug Report Code (Required)

IT4wkMrl24ZOxPVA1YSJdvlagjgWMjt/ao0ViOptZCs9GYjyO5YUac77bRFDXenhTXxbKEWJqzkEwc2PhtrtF+4oaAesG4BywbV6FhbgeDq/aoSOCKWSSkdBGeNUBXHC057QmRFAWfh1LHgZ3EOQNvPJdALUJLn7Zwh9f6PHaOI=

Visual documentation

Environment

- FlutterFlow version: v6.6.105
- Platform: Web
- Browser name and version: Chrome
- Operating system and version affected: Windows 11

Additional Information

No response

[Alezanello]

Hello!

I wasn’t able to reproduce the issue, so it appears to be project-specific. Please contact support through the in-app chat or at support@flutterflow.io for direct assistance with this issue.