Wrong signing key being used for deployment

🧩 Reason 1: The `build.gradle` file is unlocked

When the build.gradle file is unlocked, FlutterFlow cannot automatically manage your signing configuration, which may result in the wrong key being used during deployment.

✅ Solution : Lock the `build.gradle` file

Choose this option if you don’t need to make manual edits to the file.

Locking it allows FlutterFlow to handle signing automatically.

Steps:

Open your FlutterFlow project.
Locate your build.gradle file (usually under android/app/).
Lock the file so FlutterFlow can make necessary updates automatically.

🛠️ Alternative: Manually update the signing configuration

If you need to keep the file unlocked (for custom edits), update the signing configuration manually.

In your build.gradle file, find this line:

signingConfigs.debug

Change it to:

signingConfigs.release

This ensures the correct signing configuration is applied while still allowing manual customization.

🌀 Reason 2: The project was duplicated

If your FlutterFlow project was duplicated or cloned, the new copy may not retain the original signing key configuration, which can cause deployment issues.

✅ Solution: Reconnect or recreate your signing key

You’ll need to reconnect the correct key or create a new one in FlutterFlow.

Steps:

Go to Settings → App Settings → Build in your FlutterFlow project.
Under the Android Signing section, check your current key configuration.

🔑 If you already have your old signing key

Upload your existing keystore file and use the same credentials (key alias, key password, and store password) to restore your signing configuration.

♻️ If you don’t have your old signing key

You’ll need to reset your signing key from the Google Play Console:

Open your app in the Google Play Console.
Go to Setup → App Integrity → App Signing.
Request a key reset from Google.
Once approved, download the new key and upload it to FlutterFlow under the Android Signing section.

After completing this, rebuild your app and redeploy.