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

[ivanarteta]

Operating System

macOS Tahoe 26.0.1

Environment (if applicable)

React Native 0.81.0

Firebase SDK Version

12.4.0

Firebase SDK Product(s)

Auth

Project Tooling

React native app v0.81.0

Detailed Problem Description

I’m trying to upgrade my React Native app from version 0.78.2 to 0.81.0. I’ve noticed that @react-native-firebase/auth depends on @react-native-async-storage/async-storage@1.24.0, which causes conflicts with React Native’s new architecture. In my package.json, I’m using @react-native-async-storage/async-storage@2.2.0, which is compatible. Could Firebase update the dependency version so it can be used with the new React Native version?

Steps and code to reproduce issue

• Init a new React Native project with v0.81.0
• Install @react-native-async-storage/async-storage and @firebase/messaging
• npx react-native run-ios

[google-oss-bot]

I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.

[DellaBitta]

Hi @ivanarteta,

If I undestand your issue, you would like for changes to be made to the React Native Firebase SDK. If so, please reach out to that team in their GitHub Repository. Thanks!

[ivanarteta]

My bad! Thank you!

[mikehardy]

Hey @DellaBitta 👋 react-native-firebase maintainer here - the root cause of the problem @ivanarteta is having is the out of date peer dependency here for react-native-async-storage

firebase-js-sdk/packages/auth/package.json

Lines 117 to 124 in d1d898f

	"peerDependencies": {
	"@firebase/app": "0.x",
	"@react-native-async-storage/async-storage": "^1.18.1"
	},
	"peerDependenciesMeta": {
	"@react-native-async-storage/async-storage": {
	"optional": true
	}

This SDK should bump that to the ^2 semver in my opinion as versions < 2 will not work with modern reat-native, and I'll post a PR to do the same.

npm in particular has issues with package overrides so we can't handle this cleanly as a consumer app level with overrides, the only workaround people have found so far is to turn on the --legacy-peer-deps mode of npm which isn't ideal