Android AAB build failing with custom and/or generated keystore

[Everbero]

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

Summary

Android AAB builds are failing in FlutterFlow when signing the app. The issue occurs both when using my existing custom keystore and when trying to use a new keystore generated by FlutterFlow, making it impossible to update the app currently published on Google Play.

Context

• The app is already published on Google Play, therefore I must use the same keystore used in previous releases.
• The keystore, alias, and passwords have not changed.
• The same keystore can be successfully opened and verified in Keystore Explorer, confirming that the credentials are correct.
• Previous builds using this keystore worked without issues.

Problem

FlutterFlow build fails during the AAB signing step, but the error message does not clearly indicate the cause.

Additionally, the suggested troubleshooting step from support (removing the custom keystore and using the auto-generated one) does not work either, as FlutterFlow is unable to generate a working keystore for the build.

Impact

• The app cannot be updated on Google Play.
• This effectively blocks releases and makes the FlutterFlow build feature unusable for this project.

What I have already verified

• Alias name is correct
• Keystore password is correct
• Key password is correct
• Keystore file is valid and can be opened externally
• The same keystore worked in previous deployments

Expected Behavior

FlutterFlow should successfully build and sign the AAB using the existing keystore, or at least provide a clear signing error if credentials are incorrect.

Steps to Reproduce

Você pode colocar assim, bem objetivo:

Steps to Reproduce

1. Open the project in FlutterFlow.
2. Go to Settings → App Settings → Mobile Deployment → Android Keystore.
3. Upload a custom keystore previously used to sign the app on Google Play.
4. Enter the correct keystore password, key alias, and key password.
5. Save the keystore configuration.
6. Try to Deploy to Play Store.

Result

The build fails during the signing process without a clear keystore-related error.

Additional observation

The same failure also happens if:

1. The custom keystore is removed.
2. FlutterFlow is set to generate a keystore automatically.

The build still fails, suggesting the issue may not be related to the keystore credentials themselves.

Reproducible from Blank

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

Bug Report Code (Required)

IT40uOX10815rt937pbiLfpp9Rs7JFwXa78vrN57aCosfZT2BLMcec/RVERBTdeidHxAI2eaq2oW0anxhd/TKvQ5ISSVG7VzzJF+YDviRmO5R7HTFJWvdUFQQP5bGX654LbV2R0mBO5qcXxn2F2LfdzLTg/sNLLvPFQeDa/LZO4=

Visual documentation

Environment

- FlutterFlow version: Latest
- Platform: Web/Desktop
- Browser name and version: Chrome/Brave
- Operating system and version affected: Windows 6.6.6 / Web Current

Additional Information

I can't update my app, it has been a month now! There's a support ticket open #76029183