liveBook · Manning

Android signing

As explained in .NET MAUI in Action

Android signing is the process of applying a cryptographic signature to an Android application package for release and distribution.

Android signing applies a cryptographic identity to a release application package. A keystore, alias, and passwords are required, and losing them can prevent future Google Play uploads. section 12.2.2

A GitHub Actions signing workflow typically:

  • Creates or locates an RSA 2048-bit keystore. section 12.2.2
  • Stores the keystore as base64 and protects it, its alias, and passwords with GitHub Actions secrets. section 12.2.2

Signing during publish

Run dotnet publish for net7.0-android in Release mode with AndroidKeyStore enabled, the keystore path, alias, and protected key and store passwords.

How .NET MAUI in Action covers it

How deep it goes
Descends from keystore creation through secret encoding, workflow decoding, signed publishing, and artifact upload.
Examples
Uses keytool, PowerShell base64 conversion, workflow YAML, dotnet publish, and signed AAB artifact upload.
What it assumes
Assumes a .NET MAUI project and GitHub Actions workflow, while introducing keystores, aliases, signing passwords, and secrets.
What you can do after
Operate/configure a GitHub Actions job that securely builds, signs, and uploads a .NET MAUI Android AAB.
How it connects
Connects Android signing with keystores, GitHub Actions secrets, .NET MAUI workloads, MSBuild properties, and Android app bundles.
Cover of .NET MAUI in Action
liveBookmanning.com
Read .NET MAUI in Action on liveBook Get the book at manning.com

Related concepts

This explainer was generated by Manning's knowledge graph from the text of .NET MAUI in Action. The section links point to the parts of the book it draws on.