Android package name change is not applied in exported/build AAB

[AdminBlyflow]

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

After changing the Android package name from:

com.mygolfmoment.app

to:

com.blyflow.mygolfmoment

inside FlutterFlow App Details, the generated/exported Android project still uses the old package name.

The generated build.gradle file still contains:

namespace "com.mygolfmoment.app"

and Google Play Console rejects the AAB because it expects:

com.blyflow.mygolfmoment

Firebase apps, FlutterFlow App Details and Google Play configuration are all updated correctly, but FlutterFlow build/export still generates the old package name.

Expected Behavior

After updating the package name in FlutterFlow App Details, all generated Android files and AAB builds should use the new package name:

com.blyflow.mygolfmoment

including:

• namespace
• applicationId
• exported Android project
• generated AAB/APK

Steps to Reproduce

1. Open an existing FlutterFlow project.
2. Go to App Settings > App Details.
3. Change Package Name from:
   com.mygolfmoment.app
   to:
   com.blyflow.mygolfmoment
4. Save project.
5. Regenerate Firebase config files.
6. Deploy/build Android AAB from FlutterFlow.
7. Download generated code OR upload generated AAB to Google Play Console.
8. Observe that generated Android project still contains:
   namespace "com.mygolfmoment.app"
9. Google Play rejects the AAB because package name does not match.

Reproducible from Blank

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

Bug Report Code (Required)

IT5Xi87huJFOxPVd+KqJb8FVmiURNUM4RL8klcFtaAE1GKrtPLNyPODuT3JdOLyhSmw/PFv8rH0eptLJvtntCuQHAwmWfJhkzpZAUArJWkGgVqbWCKqWPXFADdlWJEuVyKW02hRdIsR0WC0g1zmEAeesdAnqHbryIVc/Lc6iUN7M+1nnAj+6Xn0Jg1ZSfCvr

Visual documentation

Environment

- FlutterFlow version: Latest web version
- Platform: Web
- Browser name and version: Google Chrome
- Operating system and version affected: macOS

Additional Information

This issue completely blocks Android deployment and Play Store publishing after migrating to a new package name/company namespace.

Firebase, Google Play Console and FlutterFlow UI all show the correct package name, but generated builds still use the old package internally.