How to Manage Signing Secrets Safely in CI

A signing key in the repo is a key in everyone's clone. Keep it in the secret store and materialize it only at build time. Here is how.

How to fix it

1. Encode and store as a secret

Base64-encode the keystore or .p12 and store it as a CI secret rather than committing the file.

2. Decode at build time

Decode the secret into a temp file just before signing, referencing it by an env var the build reads.

3. Scrub on teardown

Delete the decoded file in an always-run cleanup step so it never lingers on a shared runner.

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 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.