DocSafe v1.0.10 — recovery-import hardening

DocSafe v1.0.10 — recovery-import hardening + clearer guidance

Fixes a crash and clarifies how recovery codes work.

Crash fix

Importing a vault with a recovery code could crash if the file didn't actually contain
recovery codes (or on a memory-constrained device). The recovery-import path now fails
closed — it shows a clean "couldn't recover" message instead of crashing — and no longer
leaks a file handle on failed attempts.

Important: how recovery codes actually work

Recovery codes are stored inside the vault file. They let you open a backup of that
file by entering a code instead of the password. That means:

1. Generate the recovery codes for a vault.
2. Then back up the vault (⋮ → Save vault to device / Share vault).
3. Recovery works by re-importing that backup and choosing "Use a recovery code".

A backup made before you generated the codes will not accept them (the codes aren't in
it). The recovery-codes dialog now explains this.

No format/crypto changes — codes from 1.0.8 still work with a file that contains them.

Install

Requires Android 8.0 (API 26)+. Download docsafe-1.0.10.apk below.

• APK SHA-256: d2a6479cbee773629c410fb22eb7afbf128a4e794cbfe4559c0f1f596de4b99c
• Signing certificate SHA-256: ea684abfed2dd5f56f6da2832f8b3f6898c3317597f8c71ac554e49a5a936653