Async-storage: [@RNC/AsyncStorage]: NativeModule: AsyncStorage is null.

[hms111111]

in ios pod way,i have try everything....

[Krizzu]

We need more details to help you.
Please follow issue template and write your configuration, what you tried etc.

[shuffledex]

maybe it's related:

Loading dependency graph, done.
error: bundling failed: Error: While trying to resolve module `@react-native-community/async-storage` from file `/Users/pj/src/utils/user.js`, the package `/Users/pj/node_modules/@react-native-community/async-storage/package.json` was successfully found. However, this package itself specifies a `main` module field that could not be resolved (`/Users/pj/node_modules/@react-native-community/async-storage/lib/index.js`. Indeed, none of these files exist:

"@react-native-community/async-storage": "1.4.0"

[rafaelbomfim]

with me it does not work either.
I've tried everything.

react-native unlink @react-native-community/async-storage
react-native link @react-native-community/async-storage

pod 'RNCAsyncStorage', :path => '../node_modules/@react-native-community/async-storage'

pod install

but nothing works on ios

I dont know what to try anymore

[@RNC/AsyncStorage]: NativeModule: AsyncStorage is null.

<unknown> AsyncStorage.js:22:8 loadModuleImplementation require.js:331:6 <unknown> index.js:5 loadModuleImplementation require.js:331:6 <unknown> index.js:1 loadModuleImplementation require.js:331:6 <unknown> routes.js:3 loadModuleImplementation require.js:331:6 <unknown> index.js:9 loadModuleImplementation require.js:331:6 <unknown> index.js:6 loadModuleImplementation require.js:331:6 guardedLoadModule require.js:197:45 global code <unknown file>:0

[tido64]

Sorry to hear you have this issue. 😞 Can you try the steps I outlined here and report back: https://github.com/react-native-community/react-native-async-storage/issues/86#issuecomment-489395351

You should make sure that RNCAsyncStorage is a target in the Pods project in Xcode. If it's missing, then CocoaPods haven't linked it in yet, and would explain why you're getting AsyncStorage is null. I don't think this is specifically related AsyncStorage.

[hms111111]

@rafaelbomfim yes,i'm do the same things like you

[palexs]

In my case I had this issue on Android. The problem was that by default react-native link command assumes that protected List<ReactPackage> getPackages() method is located in MainApplication.java. In our app we moved this method to another file. To solve the issue I had to link manually.

[infiniteline]

I'm having this issue as well on iOS builds. Not using CocoaPods. Followed @tido64's suggestions from #86, but to no avail.

[Krizzu]

Just a reminder: if you're using Expo you can't get this package to work.

@infiniteline It'd be best if you could provide some more info about your setup/repro steps.

thanks.

[infiniteline]

Thanks for your reply, @Krizzu. I was able to resolve it for iOS through manual linking. Not sure why I had to resort to that? This is an ejected project that has been made into a workspace after installing Firebase. Do you think that makes a difference?

[Krizzu]

@infiniteline I'm glad you got it working. This could have been due react native link nature, where it expects a certain project structure to operate correctly.

[Vic-L]

I was on a different sheme/target. react-native link only apply the changes to the main target. Not using the pods ways though. Maybe it may help :)

[appjitsu]

also using latest expo. cant get this package to work. linking has no effect.

[Krizzu]

Hi @appjitsu
Please checkout troubleshooting docs

thanks.

[Walaa106]

Manual linking for iOS solved it for me

[HoangNamVN]

Hello Mr @Krizzu. i have same problem but i already code asyncstorage in my file and i use expo. Can u help me to fix it? i will appreciate it. I'm rookie

[Krizzu]

Hi @HoangNamVN

Unfortunately, You cannot use this package with Expo due to its architecture. You can do so by ejecting or waiting for Expo team to upgrade to Community's Async Storage.

[Tyratox]

In that case this should be stated in the README. https://facebook.github.io/react-native/docs/asyncstorage now points to this project.

EDIT: One can see that the project contains native code / doesn't work with expo as this project needs linking so tido64 makes a fair point.

[tido64]

To be fair, it is clearly stated in Expo's documentation: https://docs.expo.io/versions/latest/expokit/eject/#should-i-eject-to-expokit. And here: https://docs.expo.io/versions/latest/introduction/faq/#how-do-i-add-custom-native-code. This applies to any package containing native code, not just AsyncStorage.

[Krizzu]

Right, looks like the issue is gone. Closing this one.

[msqar]

@Krizzu Sorry to revive this but I'm still having this issue RN 0.60.4 on Android. How can I fix this? Some people say to "manually install it", but how? Never had issues on iOS, and i'm not even using pod. But Android is making me struggle.

[Krizzu]

@msqar We have instructions for manual linking. but the auto-linking feature should do it for you.

Auto linking should work out of the box if you're willing to dive why it's not happening, checkout diff comparison between RN 0.59 and 0.60 to see what changes are necessary to get it to work

[nolan12345]

问题解决方案
1，react-native unlink @react-native-community/async-storage
2，cd ios && pod install

[Arachnids]

@Krizzu Sorry to revive this but I'm still having this issue RN 0.60.4 on Android. How can I fix this? Some people say to "manually install it", but how? Never had issues on iOS, and i'm not even using pod. But Android is making me struggle.

Were you able to solve this issue? I'm suffering from the same using RN 0.60.4/5 just on Android.

@Krizzu Someone opened an issue 5 days ago, I followed your advice of cleaning the build and re-installing dependencies but sadly, no positive results just yet.

https://github.com/react-native-community/async-storage/issues/205

I'm getting the "AsyncStorage is null" error just on Android. Could you check on this, please? :)

[msqar]

@Krizzu yes, as you said... after i properly migrated to 0.60.5 autolinking started to work and everything works as expected, i haven't had to manually install it :) no errors on both Android/iOS. Thanks man!