Quick answer: Generate a release keystore, set its path and credentials in the export preset's keystore fields, and export in release mode.

Your Godot Android debug export works but the release export fails or installs unsigned because the release keystore is not configured. Setting the keystore credentials fixes it.

How to fix it

1. Generate a release keystore

Create one with keytool -genkey -v -keystore release.keystore -alias mygame -keyalg RSA -keysize 2048 -validity 10000 and store it safely; you must reuse it for every future update.

2. Set the keystore in the preset

In the Android export preset's Keystore section, set the release keystore path, alias, and both passwords. A blank release keystore field causes the release export to fail or stay unsigned.

3. Export in release mode

Export with the release (non-debug) option so Godot signs with your release keystore. A debug export uses the debug key and cannot be published to the Play Store.

Catching the ones you can't reproduce

The hardest version of this to fix is the one you can't reproduce — it only happens on a player's hardware, OS, driver, or save state, under conditions that simply aren't present on your machine. A report that says “it crashed” or “it froze” gives you nothing to act on, so the bug survives release after release while quietly costing you players.

Automatic error capture closes that gap. Each failure arrives with its full stack trace, the device and OS, the build number, and a breadcrumb trail of what the player did right before it broke, so even a failure you have never seen becomes a specific, reproducible issue. Fold identical failures into one signature ranked by how many players each hits, and your worklist sorts itself worst-first instead of arriving as a stream of vague complaints.

This is where a tool like Bugnet earns its place. Its SDK captures every Godot error automatically with the full stack trace plus device, OS, memory, build, and game-state context, folds duplicates into one grouped issue with an occurrence count, and ties each to the build it first appeared on — so you fix the problem that hurts the most players first and confirm it is gone when its signature disappears from the next release.

A crash you can name from its stack trace is a crash you can usually fix in minutes.