PasswordVault v2.4.2

Changes

• Add a Windows x64 desktop download, sharing the NSH interface and vault core with Mac.
• Identify the primary vault device and combine verified device admission with sync authorization; recover interrupted approvals without restoring revoked access.
• Improve cross-platform storage, file dialogs and rich-note editing; keep automated PR checks lightweight.

Downloads

Six packages: Android ARM64, macOS, Windows x64, iOS Simulator, Chromium extension and Web.

Windows is an unsigned portable x64 package; extract the whole folder. Browser/AI local IPC, global shortcuts, terminal handoff and recovery printing remain unavailable on Windows. Primary transfer and mobile primary hosting are not included.

Mac requires Apple Silicon / macOS 14+ and is not notarized. The iOS package is simulator-only. Preserve an encrypted backup before upgrading. A regular release does not imply completed production-security acceptance.

Installation · License · Third-party notices

PasswordVault v2.3.2

更新内容

• 新增个人密码库加密中继同步和设备授权。
• 完善图文笔记、加密附件及多设备冲突处理。

下载说明

提供 Android ARM64 APK、浏览器扩展、iOS 模拟器包、macOS ZIP 和 Web ZIP，各一个。

此版本 Mac 支持 macOS 13+、Apple Silicon 和 Intel，公共包未公证。iOS 包仅供模拟器使用，不能直接安装到 iPhone。开发预览版，升级前请保留加密备份。

许可证

PasswordVault v2.3.1

PasswordVault 2.3.1 — native clients

A coordinated release of the native Mac workspace, Android app, lightweight browser extension, standalone Web app, and iOS Simulator app. Notes, accounts, authenticator codes and wallets share the Rust vault core. Mac now has an offline rich-text editor with encrypted images and attachments; mobile and Web clients protect these new notes with read-only text summaries.

Developer preview: this is a regular GitHub Release, not a claim of production security acceptance. Independent security review, signed iPhone distribution and some hardware/migration gates remain open. Read SECURITY_MODEL.md before storing important data.

Changes in 2.3.1

• Remove shared-vault creation, membership, invitations and LAN discovery/sync from Mac and iOS. Android already omitted these controls. Existing shared records, backup metadata and historical read-only permissions remain readable.

Changes in 2.3.0

• Replace the Mac note editor with local Tiptap: headings, lists/tasks, tables, links, search/replace, undo/redo, images and file attachments. A visible toolbar and anchored color palettes make tools discoverable.
• Preserve typing focus across Return/autosave and whole-page wheel/trackpad scrolling with the title. Preview is read-only.
• Encrypt rich JSON, retained legacy originals and attachment metadata/bytes. Limits: 25 MiB per attachment and 250 MiB retained attachments per note.
• Include all attachments in authenticated V3 local/WebDAV backups, with validation and atomic restoration. An encrypted pre-upgrade snapshot is made before enabling the new format.
• Protect rich notes from incomplete editing/export on mobile and Web. Older programs reject upgraded vaults; use this release's Mac app for full rich-note editing and backups.

Upgrade/rollback: keep a verified encrypted backup before upgrading. The new format becomes active on first rich edit or attachment import. Rollback requires the complete pre-upgrade encrypted snapshot and its original password; do not open the upgraded database in an old client. Existing shared notes retain the legacy editor; this release no longer offers shared-vault management. See rich-note format and limits.

Local validation includes Rust encryption/backup failure tests, native editor lifecycle tests, 300 continuous Return/input cycles, window scrolling and color-selection regressions, plus browser and mobile builds. Physical Chinese IME candidate flows, macOS 13/Intel hardware and Touch ID remain separate acceptance gates.

Downloads and installation

Download	Requirements and installation
android-arm64-v8a.apk	Most current Android phones; Android 7.0+ (system Autofill: Android 8+). Install the APK.
android-x86_64.apk	Android x86_64 devices/emulators, Android 7.0+. No 32-bit ARM build.
macos-universal-development.zip	macOS 13+, Apple Silicon or Intel. Extract and move PasswordVault.app to Applications. Ad-hoc signed, not notarized.
chromium-extension.zip	Extract to a permanent folder; Chrome/Edge Extensions → Developer mode → Load unpacked → select the folder containing manifest.json.
web.zip	Extract and serve over HTTPS or localhost. Open index.html through the server. This is a separate vault from the extension and desktop.
ios-simulator.zip	A Mac with a compatible Xcode iOS Simulator. Not an IPA; cannot install on an iPhone. Extract; run xcrun simctl install booted PasswordVault.app. The bundled executable architecture/runtime determine simulator compatibility.
source.zip	Source for all clients, including the iOS app and AutoFill extension. Follow the platform READMEs to build; device installation requires eligible provisioning.

All client versions are 2.3.1. BUILD.json identifies the exact source commit, build numbers and distribution limitations. Verify downloads with shasum -a 256 -c SHA256SUMS after downloading the complete asset set.

Android installation identity

Public APKs are non-debuggable and signed with the reviewed release certificate in SIGNING-CERTIFICATE-SHA256.txt. The native app uses com.securepass.vault.nativepreview, so it coexists with the legacy Flutter application; legacy data is not automatically migrated. Use an encrypted backup and an explicit import.

Previous locally installed native debug/compact builds use a different signing key and cannot be updated with these public APKs. Preserve and verify an encrypted backup before switching installations. Do not uninstall the only copy of a vault to resolve a signature error. This release does not replace the legacy Android App Bundle in an app store.

Mac installation and Touch ID

The downloadable development app is ad-hoc signed, not Developer ID signed/notarized. macOS may block the first launch. If you trust the downloaded build, first attempt to open it, then use System Settings → Privacy & Security → Open Anyway where available; this grants an exception for this app. Managed Macs may prevent exceptions. See Apple's guidance.

Touch ID/keychain enrollment is not promised in this public ad-hoc build. Use the master password, or build locally with an eligible Apple Development signing configuration as described in the Mac guide. Users of a locally signed Touch ID build should retain it until they have confirmed master-password access; changing signing identity can affect keychain access. Existing vault data is not removed by installing the application.

For first browser connection, register the extension/browser in Mac settings. After entering the Mac master password in the extension, authorized saving and current-site account access work while the main app is quit. Startup unlock is optional. Reauthorize after a helper signing change; old grants remain save-only. See browser authorization. The browser extension supports a separate independent vault as well; it does not automatically merge data.

iPhone installation options

The simulator archive needs no device provisioning. For a personal iPhone, Xcode can provision supported capabilities with a Personal Team, generally requiring renewal after seven days. This project's app plus AutoFill/App Group capabilities still require successful provisioning; a free account alone does not establish that the entire project can be installed. TestFlight, App Store or registered-device Ad Hoc distribution require an eligible paid developer team and corresponding profiles. This release includes none of those signed-device artifacts.

中文安装说明

本次更新：Mac 和 iOS 去掉共享资料库管理、邀请和局域网同步，与 Android 一致。已有共享记录、备份信息和只读限制仍可读取。2.3.0 的图文笔记、加密附件和完整备份仍包含在本版中。

升级提示：首次图文编辑或导入附件前保留加密升级快照；旧程序不能安全打开升级后的资料库。回退请恢复完整升级前快照并使用当时的密码，不能直接用旧版覆盖新库。单附件上限 25 MiB，每篇合计 250 MiB。真实中文输入法候选、macOS 13/Intel 实机与 Touch ID 仍有待验收项目。

此版本统一为 2.3.1，包含原生 Android、Mac 开发版、浏览器插件、独立 Web、iOS 模拟器包及源码。软件仍处于开发预览阶段，安全审计与部分真机验证尚未完成。

• Android：普通手机下载 android-arm64-v8a.apk；x86_64 设备下载对应 APK。使用正式发布密钥和独立原生版包名，与旧 Flutter 版共存。之前的本地调试版签名不同，无法直接覆盖；先验证加密备份，切勿为安装而直接卸载唯一的资料库。
• Mac：解压后放入「应用程序」，支持 Apple Silicon/Intel、macOS 13+。本包未公证，首次打开可能需要在「隐私与安全」中选择「仍要打开」。本包不保证 Touch ID 钥匙串注册可用，可用主密码或保留本地签名版。
• 插件：先解压，在 Chrome/Edge 扩展管理页启用开发者模式，加载含 manifest.json 的目录；不能直接加载 ZIP。更新后重新加载扩展，确认显示 2.3.1。首次需完成浏览器登记；在插件输入 Mac 主密码授权后，Mac 退出时也可保存和读取本站账号，可选择启动自动解锁。更新 helper 签名后需重新授权。
• Web：解压后用 HTTPS 或 localhost 服务打开，是独立资料库。
• iOS：本次是模拟器包及源码，不能直接安装到 iPhone。真机自用可尝试 Xcode 签名；完整 AutoFill/App Group 能力仍需合适的团队授权。TestFlight、App Store、Ad Hoc 需要付费开发者团队及相应配置。

各端不会自动同步或合并已有资料库，请使用明确的加密备份导出、导入流程。

PasswordVault v2.3.0

PasswordVault 2.3.0 — native clients

A coordinated release of the native Mac workspace, Android app, lightweight browser extension, standalone Web app, and iOS Simulator app. Notes, accounts, authenticator codes and wallets share the Rust vault core. Mac now has an offline rich-text editor with encrypted images and attachments; mobile and Web clients protect these new notes with read-only text summaries.

Developer preview: this is a regular GitHub Release, not a claim of production security acceptance. Independent security review, signed iPhone distribution and some hardware/migration gates remain open. Read SECURITY_MODEL.md before storing important data.

Changes in 2.3.0

• Replace the Mac note editor with local Tiptap: headings, lists/tasks, tables, links, search/replace, undo/redo, images and file attachments. A visible toolbar and anchored color palettes make tools discoverable.
• Preserve typing focus across Return/autosave and whole-page wheel/trackpad scrolling with the title. Preview is read-only.
• Encrypt rich JSON, retained legacy originals and attachment metadata/bytes. Limits: 25 MiB per attachment and 250 MiB retained attachments per note.
• Include all attachments in authenticated V3 local/WebDAV backups, with validation and atomic restoration. An encrypted pre-upgrade snapshot is made before enabling the new format.
• Protect rich notes from incomplete editing/export on mobile and Web. Older programs reject upgraded vaults; use this release's Mac app for full rich-note editing and backups.

Upgrade/rollback: keep a verified encrypted backup before upgrading. The new format becomes active on first rich edit or attachment import. Rollback requires the complete pre-upgrade encrypted snapshot and its original password; do not open the upgraded database in an old client. Shared notes retain the legacy editor. See rich-note format and limits.

Local validation includes Rust encryption/backup failure tests, native editor lifecycle tests, 300 continuous Return/input cycles, window scrolling and color-selection regressions, plus browser and mobile builds. Physical Chinese IME candidate flows, macOS 13/Intel hardware and Touch ID remain separate acceptance gates.

Downloads and installation

Download	Requirements and installation
android-arm64-v8a.apk	Most current Android phones; Android 7.0+ (system Autofill: Android 8+). Install the APK.
android-x86_64.apk	Android x86_64 devices/emulators, Android 7.0+. No 32-bit ARM build.
macos-universal-development.zip	macOS 13+, Apple Silicon or Intel. Extract and move PasswordVault.app to Applications. Ad-hoc signed, not notarized.
chromium-extension.zip	Extract to a permanent folder; Chrome/Edge Extensions → Developer mode → Load unpacked → select the folder containing manifest.json.
web.zip	Extract and serve over HTTPS or localhost. Open index.html through the server. This is a separate vault from the extension and desktop.
ios-simulator.zip	A Mac with a compatible Xcode iOS Simulator. Not an IPA; cannot install on an iPhone. Extract; run xcrun simctl install booted PasswordVault.app. The bundled executable architecture/runtime determine simulator compatibility.
source.zip	Source for all clients, including the iOS app and AutoFill extension. Follow the platform READMEs to build; device installation requires eligible provisioning.

All client versions are 2.3.0. BUILD.json identifies the exact source commit, build numbers and distribution limitations. Verify downloads with shasum -a 256 -c SHA256SUMS after downloading the complete asset set.

Android installation identity

Public APKs are non-debuggable and signed with the reviewed release certificate in SIGNING-CERTIFICATE-SHA256.txt. The native app uses com.securepass.vault.nativepreview, so it coexists with the legacy Flutter application; legacy data is not automatically migrated. Use an encrypted backup and an explicit import.

Previous locally installed native debug/compact builds use a different signing key and cannot be updated with these public APKs. Preserve and verify an encrypted backup before switching installations. Do not uninstall the only copy of a vault to resolve a signature error. This release does not replace the legacy Android App Bundle in an app store.

Mac installation and Touch ID

The downloadable development app is ad-hoc signed, not Developer ID signed/notarized. macOS may block the first launch. If you trust the downloaded build, first attempt to open it, then use System Settings → Privacy & Security → Open Anyway where available; this grants an exception for this app. Managed Macs may prevent exceptions. See Apple's guidance.

Touch ID/keychain enrollment is not promised in this public ad-hoc build. Use the master password, or build locally with an eligible Apple Development signing configuration as described in the Mac guide. Users of a locally signed Touch ID build should retain it until they have confirmed master-password access; changing signing identity can affect keychain access. Existing vault data is not removed by installing the application.

For first browser connection, register the extension/browser in Mac settings. After entering the Mac master password in the extension, authorized saving and current-site account access work while the main app is quit. Startup unlock is optional. Reauthorize after a helper signing change; old grants remain save-only. See browser authorization. The browser extension supports a separate independent vault as well; it does not automatically merge data.

iPhone installation options

The simulator archive needs no device provisioning. For a personal iPhone, Xcode can provision supported capabilities with a Personal Team, generally requiring renewal after seven days. This project's app plus AutoFill/App Group capabilities still require successful provisioning; a free account alone does not establish that the entire project can be installed. TestFlight, App Store or registered-device Ad Hoc distribution require an eligible paid developer team and corresponding profiles. This release includes none of those signed-device artifacts.

中文安装说明

本次更新：Mac 改为完整图文编辑器，支持常显工具栏、列表/任务、表格、查找替换、图片和附件；修复回车焦点、整页滚轮滚动和颜色弹窗定位。图文与附件统一加密，完整加密备份包含附件。手机与 Web 对新笔记仅显示只读摘要，完整编辑和备份请使用本版 Mac。

升级提示：首次图文编辑或导入附件前保留加密升级快照；旧程序不能安全打开升级后的资料库。回退请恢复完整升级前快照并使用当时的密码，不能直接用旧版覆盖新库。单附件上限 25 MiB，每篇合计 250 MiB。真实中文输入法候选、macOS 13/Intel 实机与 Touch ID 仍有待验收项目。

此版本统一为 2.3.0，包含原生 Android、Mac 开发版、浏览器插件、独立 Web、iOS 模拟器包及源码。软件仍处于开发预览阶段，安全审计与部分真机验证尚未完成。

• Android：普通手机下载 android-arm64-v8a.apk；x86_64 设备下载对应 APK。使用正式发布密钥和独立原生版包名，与旧 Flutter 版共存。之前的本地调试版签名不同，无法直接覆盖；先验证加密备份，切勿为安装而直接卸载唯一的资料库。
• Mac：解压后放入「应用程序」，支持 Apple Silicon/Intel、macOS 13+。本包未公证，首次打开可能需要在「隐私与安全」中选择「仍要打开」。本包不保证 Touch ID 钥匙串注册可用，可用主密码或保留本地签名版。
• 插件：先解压，在 Chrome/Edge 扩展管理页启用开发者模式，加载含 manifest.json 的目录；不能直接加载 ZIP。更新后重新加载扩展，确认显示 2.3.0。首次需完成浏览器登记；在插件输入 Mac 主密码授权后，Mac 退出时也可保存和读取本站账号，可选择启动自动解锁。更新 helper 签名后需重新授权。
• Web：解压后用 HTTPS 或 localhost 服务打开，是独立资料库。
• iOS：本次是模拟器包及源码，不能直接安装到 iPhone。真机自用可尝试 Xcode 签名；完整 AutoFill/App Group 能力仍需合适的团队授权。TestFlight、App Store、Ad Hoc 需要付费开发者团队及相应配置。

各端不会自动同步或合并已有资料库，请使用明确的加密备份导出、导入流程。

PasswordVault v2.2.11

PasswordVault 2.2.11 — native clients

A coordinated release of the native Mac workspace, Android app, lightweight browser extension, standalone Web app, and iOS Simulator app. Notes, accounts, authenticator codes and wallets share the Rust vault core. Mac has a live Markdown editor; Android Notes scroll as one page with a refreshed account editor.

Developer preview: this is a regular GitHub Release, not a claim of production security acceptance. Independent security review, signed iPhone distribution and some hardware/migration gates remain open. Read SECURITY_MODEL.md before storing important data.

Changes in 2.2.11

• Save confirmed login/signup credentials while the Mac app is quit. Encrypted offline staging retries only while items remain pending, with atomic delivery receipts to avoid duplicates.
• Authorize current-site account lookup, masked password reveal and fill using the Mac master password in the extension. The toolbar shows the available account count.
• Opt into Mac startup unlock during authorization. Legacy save-only grants retain their scope; manual/system locks remain effective during the running session.
• Show the extension version and a Mac launch icon in the popup header. Missing native connections offer GitHub downloads and registration guidance.
• Keep native helpers short-lived. Android and iOS receive coordinated version updates with their existing session and data behavior preserved.

Downloads and installation

Download	Requirements and installation
android-arm64-v8a.apk	Most current Android phones; Android 7.0+ (system Autofill: Android 8+). Install the APK.
android-x86_64.apk	Android x86_64 devices/emulators, Android 7.0+. No 32-bit ARM build.
macos-universal-development.zip	macOS 13+, Apple Silicon or Intel. Extract and move PasswordVault.app to Applications. Ad-hoc signed, not notarized.
chromium-extension.zip	Extract to a permanent folder; Chrome/Edge Extensions → Developer mode → Load unpacked → select the folder containing manifest.json.
web.zip	Extract and serve over HTTPS or localhost. Open index.html through the server. This is a separate vault from the extension and desktop.
ios-simulator.zip	A Mac with a compatible Xcode iOS Simulator. Not an IPA; cannot install on an iPhone. Extract; run xcrun simctl install booted PasswordVault.app. The bundled executable architecture/runtime determine simulator compatibility.
source.zip	Source for all clients, including the iOS app and AutoFill extension. Follow the platform READMEs to build; device installation requires eligible provisioning.

All client versions are 2.2.11. BUILD.json identifies the exact source commit, build numbers and distribution limitations. Verify downloads with shasum -a 256 -c SHA256SUMS after downloading the complete asset set.

Android installation identity

Public APKs are non-debuggable and signed with the reviewed release certificate in SIGNING-CERTIFICATE-SHA256.txt. The native app uses com.securepass.vault.nativepreview, so it coexists with the legacy Flutter application; legacy data is not automatically migrated. Use an encrypted backup and an explicit import.

Previous locally installed native debug/compact builds use a different signing key and cannot be updated with these public APKs. Preserve and verify an encrypted backup before switching installations. Do not uninstall the only copy of a vault to resolve a signature error. This release does not replace the legacy Android App Bundle in an app store.

Mac installation and Touch ID

The downloadable development app is ad-hoc signed, not Developer ID signed/notarized. macOS may block the first launch. If you trust the downloaded build, first attempt to open it, then use System Settings → Privacy & Security → Open Anyway where available; this grants an exception for this app. Managed Macs may prevent exceptions. See Apple's guidance.

Touch ID/keychain enrollment is not promised in this public ad-hoc build. Use the master password, or build locally with an eligible Apple Development signing configuration as described in the Mac guide. Users of a locally signed Touch ID build should retain it until they have confirmed master-password access; changing signing identity can affect keychain access. Existing vault data is not removed by installing the application.

For first browser connection, register the extension/browser in Mac settings. After entering the Mac master password in the extension, authorized saving and current-site account access work while the main app is quit. Startup unlock is optional. Reauthorize after a helper signing change; old grants remain save-only. See browser authorization. The browser extension supports a separate independent vault as well; it does not automatically merge data.

iPhone installation options

The simulator archive needs no device provisioning. For a personal iPhone, Xcode can provision supported capabilities with a Personal Team, generally requiring renewal after seven days. This project's app plus AutoFill/App Group capabilities still require successful provisioning; a free account alone does not establish that the entire project can be installed. TestFlight, App Store or registered-device Ad Hoc distribution require an eligible paid developer team and corresponding profiles. This release includes none of those signed-device artifacts.

中文安装说明

本次更新：插件支持 Mac 退出时保存、授权读取和填充当前网站账号，显示数量角标；可选择 Mac 启动自动解锁。顶部新增版本号与打开 Mac 入口，未检测到连接时提供 GitHub 下载与登记提示。原有 Android/iOS 功能保留。

此版本统一为 2.2.11，包含原生 Android、Mac 开发版、浏览器插件、独立 Web、iOS 模拟器包及源码。软件仍处于开发预览阶段，安全审计与部分真机验证尚未完成。

• Android：普通手机下载 android-arm64-v8a.apk；x86_64 设备下载对应 APK。使用正式发布密钥和独立原生版包名，与旧 Flutter 版共存。之前的本地调试版签名不同，无法直接覆盖；先验证加密备份，切勿为安装而直接卸载唯一的资料库。
• Mac：解压后放入「应用程序」，支持 Apple Silicon/Intel、macOS 13+。本包未公证，首次打开可能需要在「隐私与安全」中选择「仍要打开」。本包不保证 Touch ID 钥匙串注册可用，可用主密码或保留本地签名版。
• 插件：先解压，在 Chrome/Edge 扩展管理页启用开发者模式，加载含 manifest.json 的目录；不能直接加载 ZIP。更新后重新加载扩展，确认显示 2.2.11。首次需完成浏览器登记；在插件输入 Mac 主密码授权后，Mac 退出时也可保存和读取本站账号，可选择启动自动解锁。更新 helper 签名后需重新授权。
• Web：解压后用 HTTPS 或 localhost 服务打开，是独立资料库。
• iOS：本次是模拟器包及源码，不能直接安装到 iPhone。真机自用可尝试 Xcode 签名；完整 AutoFill/App Group 能力仍需合适的团队授权。TestFlight、App Store、Ad Hoc 需要付费开发者团队及相应配置。

各端不会自动同步或合并已有资料库，请使用明确的加密备份导出、导入流程。

PasswordVault v2.2.3

PasswordVault 2.2.3 — native clients

A coordinated release of the native Mac workspace, Android app, lightweight browser extension, standalone Web app, and iOS Simulator app. Notes, accounts, authenticator codes and wallets share the Rust vault core. Mac has a live Markdown editor; Android Notes scroll as one page with a refreshed account editor.

Developer preview: this is a regular GitHub Release, not a claim of production security acceptance. Independent security review, signed iPhone distribution and some hardware/migration gates remain open. Read SECURITY_MODEL.md before storing important data.

Changes in 2.2.3

• Fix the extension's Open Mac app button when PasswordVault is not running. The native host now waits for the macOS launch result before replying, instead of reporting success and exiting too soon.
• Failed or timed-out launches return a connection error. Existing browser registration and vault unlocking are still required; opening the app does not bypass authentication.
• Include regression coverage for cold launch, reopening, invalid extension origins and failed launches using a disposable app. Other clients receive coordinated version updates without behavior changes.

Downloads and installation

Download	Requirements and installation
android-arm64-v8a.apk	Most current Android phones; Android 7.0+ (system Autofill: Android 8+). Install the APK.
android-x86_64.apk	Android x86_64 devices/emulators, Android 7.0+. No 32-bit ARM build.
macos-universal-development.zip	macOS 13+, Apple Silicon or Intel. Extract and move PasswordVault.app to Applications. Ad-hoc signed, not notarized.
chromium-extension.zip	Extract to a permanent folder; Chrome/Edge Extensions → Developer mode → Load unpacked → select the folder containing manifest.json.
web.zip	Extract and serve over HTTPS or localhost. Open index.html through the server. This is a separate vault from the extension and desktop.
ios-simulator.zip	A Mac with a compatible Xcode iOS Simulator. Not an IPA; cannot install on an iPhone. Extract; run xcrun simctl install booted PasswordVault.app. The bundled executable architecture/runtime determine simulator compatibility.
source.zip	Source for all clients, including the iOS app and AutoFill extension. Follow the platform READMEs to build; device installation requires eligible provisioning.

All client versions are 2.2.3. BUILD.json identifies the exact source commit, build numbers and distribution limitations. Verify downloads with shasum -a 256 -c SHA256SUMS after downloading the complete asset set.

Android installation identity

Public APKs are non-debuggable and signed with the reviewed release certificate in SIGNING-CERTIFICATE-SHA256.txt. The native app uses com.securepass.vault.nativepreview, so it coexists with the legacy Flutter application; legacy data is not automatically migrated. Use an encrypted backup and an explicit import.

Previous locally installed native debug/compact builds use a different signing key and cannot be updated with these public APKs. Preserve and verify an encrypted backup before switching installations. Do not uninstall the only copy of a vault to resolve a signature error. This release does not replace the legacy Android App Bundle in an app store.

Mac installation and Touch ID

The downloadable development app is ad-hoc signed, not Developer ID signed/notarized. macOS may block the first launch. If you trust the downloaded build, first attempt to open it, then use System Settings → Privacy & Security → Open Anyway where available; this grants an exception for this app. Managed Macs may prevent exceptions. See Apple's guidance.

Touch ID/keychain enrollment is not promised in this public ad-hoc build. Use the master password, or build locally with an eligible Apple Development signing configuration as described in the Mac guide. Users of a locally signed Touch ID build should retain it until they have confirmed master-password access; changing signing identity can affect keychain access. Existing vault data is not removed by installing the application.

For browser connection, open and unlock Mac, then register the extension/browser in Mac settings. The browser extension supports a separate independent vault as well; it does not automatically merge data.

iPhone installation options

The simulator archive needs no device provisioning. For a personal iPhone, Xcode can provision supported capabilities with a Personal Team, generally requiring renewal after seven days. This project's app plus AutoFill/App Group capabilities still require successful provisioning; a free account alone does not establish that the entire project can be installed. TestFlight, App Store or registered-device Ad Hoc distribution require an eligible paid developer team and corresponding profiles. This release includes none of those signed-device artifacts.

中文安装说明

本次更新：Android 短暂切后台不再反复要求解锁，仍按空闲时间、锁屏与手动锁定执行；移除 Android 共享资料库管理和局域网同步，保留已有资料与备份兼容。Mac 新增锁屏／切换用户、睡眠的独立锁定选项，默认仍立即锁定。

此版本统一为 2.2.3，包含原生 Android、Mac 开发版、浏览器插件、独立 Web、iOS 模拟器包及源码。软件仍处于开发预览阶段，安全审计与部分真机验证尚未完成。

• Android：普通手机下载 android-arm64-v8a.apk；x86_64 设备下载对应 APK。使用正式发布密钥和独立原生版包名，与旧 Flutter 版共存。之前的本地调试版签名不同，无法直接覆盖；先验证加密备份，切勿为安装而直接卸载唯一的资料库。
• Mac：解压后放入「应用程序」，支持 Apple Silicon/Intel、macOS 13+。本包未公证，首次打开可能需要在「隐私与安全」中选择「仍要打开」。本包不保证 Touch ID 钥匙串注册可用，可用主密码或保留本地签名版。
• 插件：先解压，在 Chrome/Edge 扩展管理页启用开发者模式，加载含 manifest.json 的目录；不能直接加载 ZIP。更新后重新加载扩展，确认显示 2.2.3。连接 Mac 需先打开并解锁桌面端、完成浏览器登记。
• Web：解压后用 HTTPS 或 localhost 服务打开，是独立资料库。
• iOS：本次是模拟器包及源码，不能直接安装到 iPhone。真机自用可尝试 Xcode 签名；完整 AutoFill/App Group 能力仍需合适的团队授权。TestFlight、App Store、Ad Hoc 需要付费开发者团队及相应配置。

各端不会自动同步或合并已有资料库，请使用明确的加密备份导出、导入流程。

PasswordVault v2.2.2

PasswordVault 2.2.2 — native clients

A coordinated release of the native Mac workspace, Android app, lightweight browser extension, standalone Web app, and iOS Simulator app. Notes, accounts, authenticator codes and wallets share the Rust vault core. Mac has a live Markdown editor; Android Notes scroll as one page with a refreshed account editor.

Developer preview: this is a regular GitHub Release, not a claim of production security acceptance. Independent security review, signed iPhone distribution and some hardware/migration gates remain open. Read SECURITY_MODEL.md before storing important data.

Changes in 2.2.2

• Android keeps its main workspace unlocked across brief app switches until the configured idle deadline, while screen/manual locking remains immediate. Background edits are checkpointed as encrypted drafts; process restart still requires authentication.
• Android shared-vault management, invitations and LAN synchronization are removed. Existing records, encrypted backups and historical read-only permissions remain intact. Mac and iOS sharing behavior is unchanged.
• Mac adds separate screen-lock/session-switch and sleep preferences, both defaulting to immediate locking. Idle locking remains independent; preferences are stored inside the encrypted vault.
• Add protected, versioned Android device-build artifacts without publishing unrelated platforms. The coordinated 2.2.2 release still includes every native client.

Downloads and installation

Download	Requirements and installation
android-arm64-v8a.apk	Most current Android phones; Android 7.0+ (system Autofill: Android 8+). Install the APK.
android-x86_64.apk	Android x86_64 devices/emulators, Android 7.0+. No 32-bit ARM build.
macos-universal-development.zip	macOS 13+, Apple Silicon or Intel. Extract and move PasswordVault.app to Applications. Ad-hoc signed, not notarized.
chromium-extension.zip	Extract to a permanent folder; Chrome/Edge Extensions → Developer mode → Load unpacked → select the folder containing manifest.json.
web.zip	Extract and serve over HTTPS or localhost. Open index.html through the server. This is a separate vault from the extension and desktop.
ios-simulator.zip	A Mac with a compatible Xcode iOS Simulator. Not an IPA; cannot install on an iPhone. Extract; run xcrun simctl install booted PasswordVault.app. The bundled executable architecture/runtime determine simulator compatibility.
source.zip	Source for all clients, including the iOS app and AutoFill extension. Follow the platform READMEs to build; device installation requires eligible provisioning.

All client versions are 2.2.2. BUILD.json identifies the exact source commit, build numbers and distribution limitations. Verify downloads with shasum -a 256 -c SHA256SUMS after downloading the complete asset set.

Android installation identity

Public APKs are non-debuggable and signed with the reviewed release certificate in SIGNING-CERTIFICATE-SHA256.txt. The native app uses com.securepass.vault.nativepreview, so it coexists with the legacy Flutter application; legacy data is not automatically migrated. Use an encrypted backup and an explicit import.

Previous locally installed native debug/compact builds use a different signing key and cannot be updated with these public APKs. Preserve and verify an encrypted backup before switching installations. Do not uninstall the only copy of a vault to resolve a signature error. This release does not replace the legacy Android App Bundle in an app store.

Mac installation and Touch ID

The downloadable development app is ad-hoc signed, not Developer ID signed/notarized. macOS may block the first launch. If you trust the downloaded build, first attempt to open it, then use System Settings → Privacy & Security → Open Anyway where available; this grants an exception for this app. Managed Macs may prevent exceptions. See Apple's guidance.

Touch ID/keychain enrollment is not promised in this public ad-hoc build. Use the master password, or build locally with an eligible Apple Development signing configuration as described in the Mac guide. Users of a locally signed Touch ID build should retain it until they have confirmed master-password access; changing signing identity can affect keychain access. Existing vault data is not removed by installing the application.

For browser connection, open and unlock Mac, then register the extension/browser in Mac settings. The browser extension supports a separate independent vault as well; it does not automatically merge data.

iPhone installation options

The simulator archive needs no device provisioning. For a personal iPhone, Xcode can provision supported capabilities with a Personal Team, generally requiring renewal after seven days. This project's app plus AutoFill/App Group capabilities still require successful provisioning; a free account alone does not establish that the entire project can be installed. TestFlight, App Store or registered-device Ad Hoc distribution require an eligible paid developer team and corresponding profiles. This release includes none of those signed-device artifacts.

中文安装说明

本次更新：Android 短暂切后台不再反复要求解锁，仍按空闲时间、锁屏与手动锁定执行；移除 Android 共享资料库管理和局域网同步，保留已有资料与备份兼容。Mac 新增锁屏／切换用户、睡眠的独立锁定选项，默认仍立即锁定。

此版本统一为 2.2.2，包含原生 Android、Mac 开发版、浏览器插件、独立 Web、iOS 模拟器包及源码。软件仍处于开发预览阶段，安全审计与部分真机验证尚未完成。

• Android：普通手机下载 android-arm64-v8a.apk；x86_64 设备下载对应 APK。使用正式发布密钥和独立原生版包名，与旧 Flutter 版共存。之前的本地调试版签名不同，无法直接覆盖；先验证加密备份，切勿为安装而直接卸载唯一的资料库。
• Mac：解压后放入「应用程序」，支持 Apple Silicon/Intel、macOS 13+。本包未公证，首次打开可能需要在「隐私与安全」中选择「仍要打开」。本包不保证 Touch ID 钥匙串注册可用，可用主密码或保留本地签名版。
• 插件：先解压，在 Chrome/Edge 扩展管理页启用开发者模式，加载含 manifest.json 的目录；不能直接加载 ZIP。更新后重新加载扩展，确认显示 2.2.2。连接 Mac 需先打开并解锁桌面端、完成浏览器登记。
• Web：解压后用 HTTPS 或 localhost 服务打开，是独立资料库。
• iOS：本次是模拟器包及源码，不能直接安装到 iPhone。真机自用可尝试 Xcode 签名；完整 AutoFill/App Group 能力仍需合适的团队授权。TestFlight、App Store、Ad Hoc 需要付费开发者团队及相应配置。

各端不会自动同步或合并已有资料库，请使用明确的加密备份导出、导入流程。

PasswordVault v2.2.1

PasswordVault 2.2.1 — native clients

A coordinated release of the native Mac workspace, Android app, lightweight browser extension, standalone Web app, and iOS Simulator app. Notes, accounts, authenticator codes and wallets share the Rust vault core. Mac has a live Markdown editor; Android Notes scroll as one page with a refreshed account editor.

Developer preview: this is a regular GitHub Release, not a claim of production security acceptance. Independent security review, signed iPhone distribution and some hardware/migration gates remain open. Read SECURITY_MODEL.md before storing important data.

Downloads and installation

Download	Requirements and installation
android-arm64-v8a.apk	Most current Android phones; Android 7.0+ (system Autofill: Android 8+). Install the APK.
android-x86_64.apk	Android x86_64 devices/emulators, Android 7.0+. No 32-bit ARM build.
macos-universal-development.zip	macOS 13+, Apple Silicon or Intel. Extract and move PasswordVault.app to Applications. Ad-hoc signed, not notarized.
chromium-extension.zip	Extract to a permanent folder; Chrome/Edge Extensions → Developer mode → Load unpacked → select the folder containing manifest.json.
web.zip	Extract and serve over HTTPS or localhost. Open index.html through the server. This is a separate vault from the extension and desktop.
ios-simulator.zip	A Mac with a compatible Xcode iOS Simulator. Not an IPA; cannot install on an iPhone. Extract; run xcrun simctl install booted PasswordVault.app. The bundled executable architecture/runtime determine simulator compatibility.
source.zip	Source for all clients, including the iOS app and AutoFill extension. Follow the platform READMEs to build; device installation requires eligible provisioning.

All client versions are 2.2.1. BUILD.json identifies the exact source commit, build numbers and distribution limitations. Verify downloads with shasum -a 256 -c SHA256SUMS after downloading the complete asset set.

Android installation identity

Public APKs are non-debuggable and signed with the reviewed release certificate in SIGNING-CERTIFICATE-SHA256.txt. The native app uses com.securepass.vault.nativepreview, so it coexists with the legacy Flutter application; legacy data is not automatically migrated. Use an encrypted backup and an explicit import.

Previous locally installed native debug/compact builds use a different signing key and cannot be updated with these public APKs. Preserve and verify an encrypted backup before switching installations. Do not uninstall the only copy of a vault to resolve a signature error. This release does not replace the legacy Android App Bundle in an app store.

Mac installation and Touch ID

The downloadable development app is ad-hoc signed, not Developer ID signed/notarized. macOS may block the first launch. If you trust the downloaded build, first attempt to open it, then use System Settings → Privacy & Security → Open Anyway where available; this grants an exception for this app. Managed Macs may prevent exceptions. See Apple's guidance.

Touch ID/keychain enrollment is not promised in this public ad-hoc build. Use the master password, or build locally with an eligible Apple Development signing configuration as described in the Mac guide. Users of a locally signed Touch ID build should retain it until they have confirmed master-password access; changing signing identity can affect keychain access. Existing vault data is not removed by installing the application.

For browser connection, open and unlock Mac, then register the extension/browser in Mac settings. The browser extension supports a separate independent vault as well; it does not automatically merge data.

iPhone installation options

The simulator archive needs no device provisioning. For a personal iPhone, Xcode can provision supported capabilities with a Personal Team, generally requiring renewal after seven days. This project's app plus AutoFill/App Group capabilities still require successful provisioning; a free account alone does not establish that the entire project can be installed. TestFlight, App Store or registered-device Ad Hoc distribution require an eligible paid developer team and corresponding profiles. This release includes none of those signed-device artifacts.

中文安装说明

此版本统一为 2.2.1，包含原生 Android、Mac 开发版、浏览器插件、独立 Web、iOS 模拟器包及源码。软件仍处于开发预览阶段，安全审计与部分真机验证尚未完成。

• Android：普通手机下载 android-arm64-v8a.apk；x86_64 设备下载对应 APK。使用正式发布密钥和独立原生版包名，与旧 Flutter 版共存。之前的本地调试版签名不同，无法直接覆盖；先验证加密备份，切勿为安装而直接卸载唯一的资料库。
• Mac：解压后放入「应用程序」，支持 Apple Silicon/Intel、macOS 13+。本包未公证，首次打开可能需要在「隐私与安全」中选择「仍要打开」。本包不保证 Touch ID 钥匙串注册可用，可用主密码或保留本地签名版。
• 插件：先解压，在 Chrome/Edge 扩展管理页启用开发者模式，加载含 manifest.json 的目录；不能直接加载 ZIP。更新后重新加载扩展，确认显示 2.2.1。连接 Mac 需先打开并解锁桌面端、完成浏览器登记。
• Web：解压后用 HTTPS 或 localhost 服务打开，是独立资料库。
• iOS：本次是模拟器包及源码，不能直接安装到 iPhone。真机自用可尝试 Xcode 签名；完整 AutoFill/App Group 能力仍需合适的团队授权。TestFlight、App Store、Ad Hoc 需要付费开发者团队及相应配置。

各端不会自动同步或合并已有资料库，请使用明确的加密备份导出、导入流程。

PasswordVault v1.2.0

PasswordVault developer preview. Not independently audited; use synthetic credentials and review the security model before evaluation.

This release adds Codes → Add → Scan QR code on Android and iOS. Scan a single-account authenticator setup QR code, review the service and account, then save it. Camera permission denial, invalid codes, repeated detections, and save failures are handled without losing entered details. Android version: 1.2.0 (build 7).

Supported QR codes use otpauth://totp, SHA-1, and 6 digits. Refresh intervals are retained and used for code generation and export. HOTP, other algorithms/digit lengths, and Google Authenticator batch migration QR codes are not supported. Manual entry remains available.

This release also fixes code-card wrapping on narrow screens and strengthens repository rules for excluding private vault data, exports, credentials, and signing material.

All CI checks, Android signature verification, and package checksum checks complete before this release is published automatically.

English is the default UI language; Simplified Chinese is available on the lock screen and in Settings → Appearance.

Asset	Purpose
*-android-arm64-v8a.apk	Signed release APK for most recent Android devices
*-android-armeabi-v7a.apk	Signed release APK for supported 32-bit ARM devices
*-android-x86_64.apk	Signed release APK for x86_64 devices/emulators
*-android.aab	Signed Android App Bundle for maintainer distribution
*-web.zip	Self-hosted experimental Web build
*-chrome-extension.zip	Unpack and load in Chrome/Edge developer mode
SIGNING-CERTIFICATE-SHA256.txt	Expected public Android signing certificate fingerprint
BUILD.json	Source commit, tag, toolchain, and workflow URL
LICENSE, THIRD_PARTY_NOTICES.md, INSTALL.md	Licensing and installation guidance
SHA256SUMS	SHA-256 checksums for the complete asset inventory

Verify downloaded files with shasum -a 256 -c SHA256SUMS (macOS) or sha256sum -c SHA256SUMS (Linux). Checksums detect corruption; verify the release's source and signing identity separately.

Do not install this over a valuable existing vault without a tested backup. Signing keys used in private development must not be reused for public releases. No app store availability is implied.

中文：本次新增手机端「验证码 → 添加 → 扫描二维码」，支持 SHA-1、6 位单账号 TOTP，保留刷新间隔并支持保存失败重试；暂不支持 HOTP 和批量迁移二维码。这是开发预览版，未经独立安全审计，请使用测试凭据。默认英文，可切换简体中文。升级前请验证备份；各平台限制与已知问题见仓库的安全模型文档。

PasswordVault v1.1.0-preview.4

PasswordVault developer preview. Not independently audited; use synthetic credentials and review the security model before evaluation.

This preview includes the redesigned Accounts-first workspace, responsive navigation and account cards, persistent search, updated lock screen and password generator, and revised light/dark themes. Android version: 1.1.0 (build 6).

All CI checks, Android signature verification, and package checksum checks complete before this release is published automatically.

English is the default UI language; Simplified Chinese is available on the lock screen and in Settings → Appearance.

Asset	Purpose
*-android-arm64-v8a.apk	Signed release APK for most recent Android devices
*-android-armeabi-v7a.apk	Signed release APK for supported 32-bit ARM devices
*-android-x86_64.apk	Signed release APK for x86_64 devices/emulators
*-android.aab	Signed Android App Bundle for maintainer distribution
*-web.zip	Self-hosted experimental Web build
*-chrome-extension.zip	Unpack and load in Chrome/Edge developer mode
SIGNING-CERTIFICATE-SHA256.txt	Expected public Android signing certificate fingerprint
BUILD.json	Source commit, tag, toolchain, and workflow URL
LICENSE, THIRD_PARTY_NOTICES.md, INSTALL.md	Licensing and installation guidance
SHA256SUMS	SHA-256 checksums for the complete asset inventory

Verify downloaded files with shasum -a 256 -c SHA256SUMS (macOS) or sha256sum -c SHA256SUMS (Linux). Checksums detect corruption; verify the release's source and signing identity separately.

Do not install this over a valuable existing vault without a tested backup. Signing keys used in private development must not be reused for public releases. No app store availability is implied.

中文：这是开发预览版，未经独立安全审计，请使用测试凭据。默认英文，可切换简体中文。升级前请验证备份；各平台限制与已知问题见仓库的安全模型文档。