async-storage

Fixes

• tvOS support (#451) 8e6c8cb
• Autolinking when using Xcode 12 (#442) 0ba7726
• Android database locale issues (#423) 9823e89
• Windows errors reported from getAllKeys/clear (#424) b1b5bcf
• Add flow annotation to index & hooks (#429) 979796c
• Add useAsyncStorage to async-storage-mock.js (#425) 8bb6640

https://github.com/react-native-community/react-native-async-storage/compare/v1.12.0...v1.12.1

Features

• Add support for enabled TurboModules in Expo (#418) ae2c675

Docs

Since the last release, many documentation PRs have landed. Thanks everyone for contribution 🎉

https://github.com/react-native-community/react-native-async-storage/compare/v1.11.0...v1.12.0

Features

• Allow Async Storage to be used in Expo (#368) f9d1924
• Pods installation on macOS (#365) 22e7583

https://github.com/react-native-community/react-native-async-storage/compare/v1.10.3...v1.11.0

Fixes

• Include Windows in npm package (#362) 5c7be33

https://github.com/react-native-community/react-native-async-storage/compare/v1.10.2...v1.10.3

Fixes

• Windows project imports (#359) 21380a0

Docs

• docs: Recommend npx pod-install for setup instructions (#358) 998900b

https://github.com/react-native-community/react-native-async-storage/compare/v1.10.1...v1.10.2

Fixes

• fix: Web and Jest mock compatibility (#351) 85c5278

Chores

• docs: API clarification (#354) 724bc68
• docs: update URL of comments of AsyncStorage.js (#348) e315614

https://github.com/react-native-community/react-native-async-storage/compare/v1.10.0...v1.10.1

Features

• Windows AsyncStorage support (#327) 3dd9e0e

Chores

• Upgrade sample apps to RN 0.61 (#329) e7e3a4f

https://github.com/react-native-community/react-native-async-storage/compare/v1.9.0...v1.10.0

Fixes

• AsyncStorageFactory types

Chores

• Updated Mobile example app

Fixes

• multiGet/multiSet methods
• Empty error thrown on calling .clearStorage

Chores

• version update to match Core

Web support added

You can now use Async Storage in your web projects. a99d805431bc59c8a7f5ebbf85f71323c83df122

https://github.com/react-native-community/react-native-async-storage/compare/v1.8.1...v1.9.0

Fixes

• Create app folder during migration if none exists (#303) 8616cbd

New platform support

• macOS implementation of AsyncStorage (#296) 05d3939

https://github.com/react-native-community/react-native-async-storage/compare/v1.8.0...v1.8.1

❗️ Features - Possible a Breaking Change for iOS Platform ❗️

Note: If you're planning on upgrade, please use v1.8.1 and up.

• Moved storage location to Application Support. Read the description below to find out more.
  Thanks @HeyImChris ! (#274) 4e49db6

Fixes

• Don’t reset the storage when the manifest file cannot be read because of iOS data protection.
  Thanks @aleh ! (#270) 36e9a12

https://github.com/react-native-community/react-native-async-storage/compare/v1.7.1...v1.8.0

(iOS) New Locations for storage - new feature overview

So far, Async Storage has used NSDocumentDirectory (and NSCachesDirectory for tvOS) location to store the manifest file, where all data is saved.

NSDocumentDirectory - This folder is visible on iOS in scenarios where you can view the Files structure. For instance, in Word/PPT/Excel, a user can tap through to this and see a folder titled "RCTAsyncLocalStorage_V1".

NSCachesDirectory - Apple documents this as a location that can get purged in low memory scenarios "the system may delete the Caches directory on rare occasions when the system is very low on disk space."

Those two location are not best place to keep user data. The new location, the Application Support directory (NSApplicationSupportDirectory), is described as "[containing] all app-specific data and support files" and it can safely contain user data. There is not risk of this purging in low memory situations and this isn’t visible to iOS users.

This feature also includes a migration process. On app startup, a check is run to see if Application Support contains the manifest file:
- If it does, do nothing
- if it does not, copy over the manifest from previous location (either NSDocumentDirectory or NSCachesDirectory)

This is considered as breaking change, as some dependencies might still use older version of AS or the one available from the React Native core. In that case, both old and new locations are used, so unexpected behavior might occur. Ideally, you’ll want to make sure that only one version of AS is used within your Application.

Thanks @HeyImChris for implementing this feature!

Features

• Web storage now can use one of three storage implementations: session storage, local storage and default idb-keyval

Chore

• Updated docs to reflect changes

Fixes

• __DEV__ global variable causing issues on web platform
• default factory options are now correctly applied (enables simple logger and error handler if options are omitted)

Chore

• Updated docs

Chore

• Updated docs

Fixes

• incorrect warning for multiRemove call (#268) 3e7fdf3

https://github.com/react-native-community/react-native-async-storage/compare/v1.7.0...v1.7.1

Release Candidate for Legacy storage.

Release Candidate for Web storage.

Release candidate for Core.