Repository navigation
6.1.6 (2026-11-06)
Storage that fails loudly instead of silently. This release makes Android writes durable, verifies that reused Keystore keys match the access policy you asked for, and stops iOS updates from deleting a secret before the replacement is accepted.
No breaking API changes. React Native 0.88.1 is the verified baseline; the New Architecture and react-native-nitro-modules 0.37.x are still required.
Android
- Builds on AGP 9. The module no longer applies the Kotlin plugin when AGP already registered the
kotlinextension, which failed configuration withCannot add extension with name 'kotlin'. Also covers AGP 10. - Writes are durable. Saving, deleting and clearing entries now use a synchronous commit and raise an error when persistence fails. Previously the write was queued with
apply()and a killed process could lose the secret without any error. - Key policy is verified. When an existing Keystore key is reused, the library checks it against the requested access control: authentication required, invalidation on biometric enrollment, authenticator type and StrongBox. A mismatch throws a message telling you to rotate the key, instead of quietly giving you weaker protection than you asked for.
- Device lock check fixed. The availability check now uses
isDeviceSecurerather thanisDeviceLocked, so protected storage is no longer reported as unavailable just because the screen is unlocked. - Authenticator policy mapping fixed. Requested biometric and device-credential policies are now translated to the correct Keystore authentication types.
- Deletes clean up after themselves.
deleteItemremoves the Keystore key even when the stored record is corrupt or unparsable, and returnsfalsewhen nothing was removed, so orphaned keys no longer accumulate. - Key rotation no longer removes legacy aliases that existing entries still point to.
iOS
- Updates no longer delete before writing. Keychain entries are updated in place, falling back to an add. A failed write can no longer wipe the last readable copy of a secret.
React hooks
skipnow cancels in-flight work and clears the state, so a late response cannot overwrite the result.- Effects replayed by React Strict Mode now publish their results instead of leaving a hook stuck in
isLoading.
Errors
causeis passed through the standardErrorconstructor, so it is a regular non-enumerablecauseand survives serialization and tooling that inspects errors.
Expo config plugin
- Importable as
react-native-sensitive-info/app.plugin.js, with type declarations shipped. - Plugin options are validated:
faceIDPermissionmust be a string ornull,enableNewArchitecturemust be a boolean. - The plugin no longer overwrites
expo.jsEngine.
Security documentation
- The README and threat model now describe what actually protects your data: the protection level depends on the requested policy and the device, so check the returned
securityLevelinstead of assuming hardware-backed storage. - Documented limits: integrity tags do not prevent replay of an older valid record, entries written by earlier versions stay readable without a tag, and metadata-only reads do not verify the tag.
For contributors
- TypeScript 7.0.2, Yarn 4.18.1 and React Native 0.88.1 in the example app.
- New
yarn typecheck:testsscript; CI checks the library, the tests and the example separately. - Release automation now targets
main.