Skip to content
All documentation

Android signing keys

Every Android build is signed with the app's key: let FluxNative create it or register your own, copy its fingerprints, and keep it safe.

Updated Oct 11, 2026

Signing key in the Build window: Generated, the SHA-1 and SHA-256 fingerprints with Copy, Replace keystore, and Download a backup
The first build makes the key and keeps it; copy its fingerprints for Firebase, or download a backup.

Create or register the key

  1. Click Build, choose Android, and find Signing key.
  2. New app: let the first build create the key, or click Create signing key now under Advanced.
  3. Already published with your own key: click Upload .jks under Advanced, before the first build.
  4. Enter the alias, the keystore password and the key password, then save.

SHA fingerprints

Advanced shows SHA-1 and SHA-256 with copy buttons. Add both to Firebase for Google sign-in; Google Maps needs the SHA-1. With Firebase connected, the assistant can add them, and the checks before a build flag missing ones.

Good to know

  • Two keys sign an app on Google Play: this keystore is the upload key (the first App Bundle registers it), and Google re-signs Play installs with its app signing key. Add both SHA pairs to Firebase; Play's are in Play Console › Protected with Play › App signing.
  • The owner can Download a backup (the .jks and its passwords) under Advanced, after confirming their password. Downloads are listed in Team › Activity.
  • Replace keystore stops installed copies from updating, and Play rejects it unless Google arranged the change.

Android builds · Firebase

Did this page help?

Which app will you launch first?

Start with a prompt, images, or Figma. No credit card required.

Start building Explore plans

Taking a little longer than usual…

Loading FluxNative