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 需要付费开发者团队及相应配置。

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