Prepare and verify Google Play distribution of the Android application #112

New Issue

hugo · 2026-08-17T19:15:16Z

hugo commented

2026-08-17 19:15:16 +00:00

Goal

Publish the audited Android client through Google Play and prove that production install and update behavior preserves secure user state.

Scope

Begin only after the Android parity/security audit passes.
Keep the production application ID de.rfc1437.ironstorage; configure version code/name, icons, adaptive/monochrome icon, feature graphic/screenshots, descriptions, category, content rating, support/privacy URLs, Data safety, encryption/export declarations, and third-party license notices.
Produce a signed, optimized Android App Bundle containing only selected ABI libraries, valid 16 KB page-size native artifacts, R8 rules, baseline profile if adopted, and separately retained native mapping/debug symbols.
Configure Play App Signing/upload keys and protected release automation without committing credentials. Review Android developer verification and current target-SDK/Play policy at release time.
Audit manifest permissions and exported app/credential/autofill components. Request camera only at the QR feature; avoid storage, contacts, accessibility, overlay, notification, and other unrelated permissions.
Use staged internal/closed testing, pre-launch reports, and representative physical devices before production rollout.
Verify a clean Play install can complete local-first setup and optional HTTPS cloning, and that biometric, repository browsing/editing, TOTP, QR transfer, Git sync, Credential Manager, and Autofill work.
Install the production update over an existing version without uninstall/reset; verify repository, config, valid Keystore records, and TOTP cache survive, migrations are atomic, and rollback/failure behavior is documented.
Document uninstall/reinstall/backup behavior truthfully; never seed app data or publish review credentials/key material.

Acceptance criteria

Play accepts/processes the production AAB and the installed artifact has the intended ID, signing lineage, SDK/ABI set, permissions, and no debug/test endpoints.
Clean-install and update-over-existing production smoke tests pass on supported arm64 devices.
App update preserves valid local state without weakening Keystore/biometric policy; uninstall/reinstall limitations match documentation.
Credential Manager/Autofill provider enablement and camera permission flows work from the Play build.
Store listing, Data safety, privacy/support material, licenses, and encryption declarations accurately match the app.
Release credentials, application tokens, GPG material, and private diagnostics are absent from repository and published artifacts.

Depends on the Android parity/security audit. Part of #87.

## Goal Publish the audited Android client through Google Play and prove that production install and update behavior preserves secure user state. ## Scope - Begin only after the Android parity/security audit passes. - Keep the production application ID `de.rfc1437.ironstorage`; configure version code/name, icons, adaptive/monochrome icon, feature graphic/screenshots, descriptions, category, content rating, support/privacy URLs, Data safety, encryption/export declarations, and third-party license notices. - Produce a signed, optimized Android App Bundle containing only selected ABI libraries, valid 16 KB page-size native artifacts, R8 rules, baseline profile if adopted, and separately retained native mapping/debug symbols. - Configure Play App Signing/upload keys and protected release automation without committing credentials. Review Android developer verification and current target-SDK/Play policy at release time. - Audit manifest permissions and exported app/credential/autofill components. Request camera only at the QR feature; avoid storage, contacts, accessibility, overlay, notification, and other unrelated permissions. - Use staged internal/closed testing, pre-launch reports, and representative physical devices before production rollout. - Verify a clean Play install can complete local-first setup and optional HTTPS cloning, and that biometric, repository browsing/editing, TOTP, QR transfer, Git sync, Credential Manager, and Autofill work. - Install the production update over an existing version without uninstall/reset; verify repository, config, valid Keystore records, and TOTP cache survive, migrations are atomic, and rollback/failure behavior is documented. - Document uninstall/reinstall/backup behavior truthfully; never seed app data or publish review credentials/key material. ## Acceptance criteria - Play accepts/processes the production AAB and the installed artifact has the intended ID, signing lineage, SDK/ABI set, permissions, and no debug/test endpoints. - Clean-install and update-over-existing production smoke tests pass on supported arm64 devices. - App update preserves valid local state without weakening Keystore/biometric policy; uninstall/reinstall limitations match documentation. - Credential Manager/Autofill provider enablement and camera permission flows work from the Play build. - Store listing, Data safety, privacy/support material, licenses, and encryption declarations accurately match the app. - Release credentials, application tokens, GPG material, and private diagnostics are absent from repository and published artifacts. Depends on the Android parity/security audit. Part of #87.

hugo added this to the 06 - Implement an Android version of the software milestone 2026-08-17 19:15:16 +00:00

hugo added the enhancement label 2026-08-17 19:15:16 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: hugo/IronStorage#112