Support @react-native-community/react-native-async-storage once AsyncStorage is removed from React-Native core
we will either fork it and create our own version of asyncstorage or include the community version when we release sdk34. sdk33 will continue to include asyncstorage and you will not receive any warnings for using it
@Brent Vatne: I'm not sure if it's just me, but when i used SDK33 all my AsyncStorage are failing. From the errors, it seems that it was removed from this forked https://github.com/expo/react-native/archive/sdk-33.0.0.tar.gz
@Rommel Manalo: perhaps you're using it wrong? https://snack.expo.io/@notbrent/excited-popsicle
@Brent Vatne: or maybe the issue is on upgrading from sdk3w. I tried with fresh sdk33 and you are right it is working. When i upgrade from 32 and commented all import from asyncstorage and the codes that uses async storage, my app works again but if is there my app fails compiling/babeling. Maybe babel-preset-expo problem,
I just blame asyncstorage because when there is an import with async storage from react-native it fails
What would be the alternative if it was removed from core? Would it require linking to install it separately?
@Zach Lanich: The core version is deprecated and not remove. Probably it will be removed in RN0.61. And keep in mind expo uses RN fork so there won't be any issues.