[ Proof ]
expo-secure-store
real upstream package — not intercepted. the app's expo-secure-store JS runs over the ExpoSecureStore native module, backed by tenant-scoped IndexedDB records encrypted with AES-GCM via WebCrypto. Bun/test environments without IndexedDB use the same encrypted record format in memory. (same golden-rule native-seam tier as expo-crypto / expo-network: upstream JS runs unmodified, every gap is a physically-absent-on-an-iOS-sim feature.) Peach iOS ExpoSecureStoreSmoke passed at 58.0.3.95%
API coverageWorking (8)
upstream validation and constantsgetItem/setItem sync APIs over the hydrated in-process cachegetItemAsync/setItemAsync/deleteItemAsync async APIsisAvailableAsynccanUseBiometricAuthentication true (Face ID enrolled)keychainService/accessGroup/requireAuthentication storage partitioningAES-GCM encrypted storage records with per-record salt/iv and tenant-scoped PBKDF2 key derivationpersists across reloads when IndexedDB is available
Missing (2)
async reads and updates of an existing requireAuthentication item scan through the simulator Face ID alert and fail with ERR_KEY_CHAIN on deny or cancel (adds and deletes never prompt, as in SecureStoreModule.swift); sync getItem/setItem block the native thread upstream and cannot wait on the alertso they do not scan. keychainAccessible does not affect browser storage access. sync reads cannot synchronously cold-load IndexedDB after a fresh worker boot; async reads hydrate the cache. all of these are honest absent-on-web semantics — apps with graceful-degradation paths behave correctly.