You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a followup to the RN v0.59 upgrade #3399. It isn't required before upgrading to v0.60, and might not be for v0.61.
When running unit tests, e.g. with tools/test , or when launching the app with the debugger, the following now goes to the console:
Warning: Async Storage has been extracted from react-native core and will be removed in a future release. It can now be installed and imported from '@react-native-community/async-storage' instead of 'react-native'. See https://github.com/react-native-community/react-native-async-storage
The core module is still there in RN master when I look now.
Marking as a priority, though, because we shouldn't get used to having a big red warning in our tests.
The README doesn't say anything about upgrading from the core module. Hopefully it's easy.
The text was updated successfully, but these errors were encountered:
Switch to actually using @react-native-community/async-storage.
The module is written in Flow under the hood, but strangely doesn't
expose the Flow types in its standard entry point. We therefore import
directly from the relevant interior file to get proper type
definitions.
This will have to be revisited in the future, as the module is
currently being completely rewritten to use TypeScript.
Fixeszulip#3570.
This is a followup to the RN v0.59 upgrade #3399. It isn't required before upgrading to v0.60, and might not be for v0.61.
When running unit tests, e.g. with
tools/test
, or when launching the app with the debugger, the following now goes to the console:The core module is still there in RN master when I look now.
Marking as a priority, though, because we shouldn't get used to having a big red warning in our tests.
The README doesn't say anything about upgrading from the core module. Hopefully it's easy.
The text was updated successfully, but these errors were encountered: