Google Play Store deployment generates different app signing key every time.

[ponneeswaran]

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,

When I try to deploy my app to google play store, the app bundle is getting signed with different key every time although I've manually enabled upload keystore in advanced settings. The flutterflow platform is not taking the uploaded keystore into factor for the deployment. I've verified the SHA1 key in the keystore file and the upload certificate key in the google play console. They match perfectly.

I'm logging this as a bug as I can replicate it consistently for the past month.

Expected Behavior

When the upload keystore is enabled in the advanced settings in Flutterflow Settings > Mobile Deployment > Google Play Store > Advanced settings.
The expected behavior is for flutterflow to not generate app signing key when an upload keystore is explicitly given.

Steps to Reproduce

1. Create a project.
2. Setup Google cloud console IAM user. give permissions. and download credentials json.
3. Setup Google Play console project and set up app signing and upload keys.
4. Upload credentials json to the Settings > Mobile Deployment > Google Play Store > Service account credentials.
5. Upload the jks java keystore file to Settings > Mobile Deployment > Google Play Store > Advanced Settings > Upload Keystore.
6. Deploy the app.

Reproducible from Blank

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

Bug Report Code (Required)

IT5Ti87huJB2octD0LrfbcJR/TosKUAjRY0zjtYadwEjHOusPOwce+LeaXFJXMu4d2xUJGH8sGAIpqnTkuzpFcIFFxGIQ755/pdQbg7dTlqVSpvSPKW0QXdDMNxjfUC15rCOihVvKtthS3ABw1OyJvK8bHTtJuezIEQvRvq1DIf7jEqDAXv3FDhmtmNecCfn

Visual documentation

Environment

- FlutterFlow version: v6.3.11
- Platform: Web / Windows Desktop
- Browser name and version: Chrome Version 140.0.7339.128 (Official Build) (64-bit)
- Operating system and version affected:

Additional Information

No response

[Alezanello]

Hello!

For issues like this, please reach out to our support team via the in-app chat or at support@flutterflow.io.

[Alezanello]

Closing this issue since we haven't heard back from you. If you are still facing the problem please submit a new issue. Thank you!