Upgrading expo-secure-store from 57.x to 58.x
Comparison of the public API of expo-secure-store 57.0.4 and 58.0.2, computed automatically from their TypeScript types. A changed signature is a candidate for a breaking change, not a certainty.
Summary
| Removed import paths | 0 |
|---|---|
| Removed exports | 0 |
| Changed signatures | 1 |
| Removed class or interface members | 0 |
| Changed class or interface members | 0 |
| Newly deprecated | 0 |
| Requirement changes (engines, peer dependencies) | 0 |
| New exports | 0 |
Removed exports
None detected.
Changed signatures
| export | Before | After |
|---|---|---|
expo-secure-store · SecureStoreOptions | { keychainService?: string | undefined; requireAuthentication?: boolean | undefined; authenticationPrompt?: string | undefined; keychainAccessible?: number | undefined; accessGroup?: string | undefined; } | { keychainService?: string | undefined; requireAuthentication?: boolean | undefined; requireConfirmation?: boolean | undefined; authenticationPrompt?: string | undefined; keychainAccessible?: number | undefined; accessGroup?: string | undefined; } |
Removed class or interface members
None detected.
Changed class or interface members
None detected.
Newly deprecated
None detected.
Requirement changes (engines, peer dependencies)
None detected.
Changelog between these versions
Text published by the package authors, shown as-is.
58.0.2
### Patch Changes
- Bump precompiled artifacts due to ABI breakage in expo-modules-jsi@58.0.6. ([#50881](https://github.com/expo/expo/pull/50881) by [@kitten](https://github.com/kitten))58.0.1
### Patch Changes
- Force-bump all packages, due to migration to changesets. ([#50762](https://github.com/expo/expo/pull/50762) by [@kitten](https://github.com/kitten))58.0.0
### 🎉 New features
- Add an Android-only `requireConfirmation` option for authenticated reads and writes. ([#48556](https://github.com/expo/expo/pull/48556) by [@skylarbarrera](https://github.com/skylarbarrera))
### 🐛 Bug fixes
- [Android] Fix `deleteItemAsync` resolving when a retried delete left the value on disk. ([#49151](https://github.com/expo/expo/pull/49151) by [@vonovak](https://github.com/vonovak))
- [iOS] Reject `deleteItemAsync` when the keychain refuses the delete, instead of resolving as if the item was removed. ([#49146](https://github.com/expo/expo/pull/49146) by [@vonovak](https://github.com/vonovak))
- [iOS] Apply `keychainAccessible` when overwriting an existing item, instead of silently keeping the accessibility it was first stored with. ([#49128](https://github.com/expo/expo/pull/49128) by [@JoRo-Code](https://github.com/JoRo-Code) and [@behenate](https://github.com/behenate))Give your AI agent these facts
Vigia is a free MCP server: your coding agent checks versions, breaking changes and vulnerabilities before it writes code. No signup, no API key.
claude mcp add --transport http vigia https://vigia.coredls.cloud/mcp
Add to CursorAdd to VS Code★ Star on GitHub
Any other MCP client
{ "mcpServers": { "vigia": { "url": "https://vigia.coredls.cloud/mcp" } } }Agent skill (SKILL.md): tells the agent when to use Vigia · GitHub Action for pull requests
Frequently asked questions
What are the breaking changes when upgrading expo-secure-store from 57 to 58?
Between expo-secure-store 57.0.4 and 58.0.2, Vigia found 0 removed exports, 1 changed signatures and 0 removed or changed class or interface members.
What became deprecated in expo-secure-store 58?
0 exports or members are newly marked as deprecated in expo-secure-store 58.0.2.
For agents
GET https://vigia.coredls.cloud/v1/packages/npm/expo-secure-store/upgrade?from=57.0.4&to=58.0.2