From 7f24634d320f44673b8f8e4f1bf544502faa9cdc Mon Sep 17 00:00:00 2001
From: harsha-vardhan-burra
+ Need help deciding how to update safely, switching phones, or upgrading from a deprecated v1.x/v2.x release? Follow our guided decision flow before installing. +
++ Select the scenario that best describes your current setup. +
++ Updating within the same major version is straightforward; jumping across legacy architectures requires special precautions. +
++ Legacy releases differ fundamentally in database schema and Android architecture from current v3.x releases. +
++ Recommended Next Step +
++ Verify your Android version meets the minimum requirement (Android 8.0+), download the recommended Stable production build, and install the APK package. +
+arm64-v8a build. If unsure about your phone's processor, download the universal APK.
+
+ + {latestProd.summary} +
++ Recommended Next Step +
++ Export your passwords as a precautionary backup, then download and install the latest Stable APK directly over your current application without uninstalling. +
+Settings → Export passwords (Google Passwords CSV format) and save the file to a secure location before updating.
+
+ Settings → Troubleshooting → Data Recovery (or Settings → Recovery in recent builds) is available as an optional in-app troubleshooting mechanism. It is not a guaranteed recovery process or a substitute for an exported backup.
+
+ + {latestProd.summary} +
++ Important Safety Notice +
++ v1.x and v2.x releases are Deprecated and have reached End of Support. Passcodes v3 was completely rewritten in Expo (React Native) with a new database architecture (Drizzle DB). Automated in-place database migration across major generational jumps carries risk of data loss. +
++ Recommended Next Step +
++ Manually export your passwords to CSV from your current app, do not uninstall Passcodes, and review official guidance or ask the maintainers before attempting an upgrade. +
+Settings → Troubleshooting → Data Recovery), but this is not a guaranteed recovery process or a substitute for an exported backup, and automatic database migration across major architectural jumps is not guaranteed.
+
+ + Refer to the v3.0.0 and v3.1.0 release notes for technical background on the Drizzle DB migration and the troubleshooting recovery workflow. +
++ Recommended Next Step +
++ Export your passwords as a CSV file on your old phone, transfer that file securely to your new phone, install the current Stable release, and import your credentials. +
++ CSV Data Safety Warning +
++ Exported password CSV files store credentials in readable, unencrypted plaintext. Keep the file strictly private, avoid cloud uploads or messaging channels, and remove temporary copies from both devices once your passwords have been successfully imported and verified. +
+Settings → Export passwords (Google Passwords CSV format). Confirm the file is saved locally to your device.
+
+ Settings → Import passwords, select your CSV file, and verify your credentials appear correctly. Securely delete temporary CSV files after verification.
+
+ + Recommended Next Step +
++ Check your installed version number on the app's home screen or under Android system App Info, then select your matching path below. +
+v3.x-Stable or v2.x-Beta).+ Withdrawn from Active Distribution +
++ Yanked releases (such as v1.2.0 or v0.1.0) were pulled due to packaging or naming defects and are not suitable for daily use. Downloads for these releases are disabled. +
++ Recommended Next Step +
++ Export any credentials currently stored in the yanked build and upgrade to the recommended Stable production build. +
+com.passwordmanager.
+
+