PWA2APP Documentation

Android signing

A production version must be signed. PWA2APP manages the keys and entrusts signing to a service separate from the build.

Generate or import

  • Generate: PWA2APP creates a keystore (RSA 4096 by default) in the signing zone.
  • Import: upload your keystore and its passwords; the certificate fingerprint is verified.

What is protected

The keystore and passwords are encrypted with AES-256-GCM envelope encryption. They are only provided to the signing service, for a given job, and every use is logged.

Sign a build

  1. Pick the Release variant and a signing key when starting the build.
  2. The build produces unsigned artifacts, then the signing service signs them and verifies the fingerprint.

Revocation

Revoking a key destroys its secrets, irreversibly on the PWA2APP side. This action asks you to confirm your password.

Play App Signing

The key you manage here is an upload key: Google may keep your application's final signing key. Check your Google Play console configuration.