Skip to content
CLIUnofficial

privy config android-key-hashes update

Replace Android signing-certificate fingerprints with diff and fresh set verification.

Usage

Section titled “Usage”
Terminal window
privy config android-key-hashes update [options]

Options

Section titled “Options”
Option Description
--dry-run Validate and print the API request without network access or credentials.
--yes Confirm this mutation or export.
--body <json> JSON body, or - to read stdin.
--file <path> JSON body file, or - to read stdin.
--allowed-android-signing-key-hashes <json> Full replacement, up to100 uppercase colon-separated SHA-256 certificate fingerprints. [] clears the list and may break native passkey/auth flows. No signing or key export.
--diff Read live state and show changes WITHOUT writing (requires login).
--allow-production Explicitly allow this production mutation; also requires --yes.

Global options such as --app, --account and --profile also apply. See the command reference overview.

Examples

Section titled “Examples”
Terminal window
privy config android-key-hashes update --allowed-android-signing-key-hashes "[]" --diff

Behavior

Section titled “Behavior”
  • Changes data: yes. Preview with --dry-run, then run with --yes and any required confirmations.
  • Scope: app
  • Before it runs: Check selected app environment and current settings.
  • Production apps: Requires --allow-production and --yes.
  • Verification: Fresh read-back of each changed field; set comparison where declared.
  • Retries: None.
Section titled “Related guides”

Inspect the full contract locally with privy schema config android-key-hashes update.

Privy CLI is an unofficial, community project by Samarth Saxena. Not affiliated with or endorsed by Privy. The Privy name and wordmark belong to Privy. It uses undocumented dashboard APIs that can change.