Getting deprecation warning using firebase in react native

Question

I am using firebase in my react native project for authentication and getting this warning even after updating my code according to modular api -

This method is deprecated (as well as all React Native Firebase namespaced API) and will be removed in the next major release as part of move to match Firebase Web modular SDK API. Please see migration guide for more details: https://rnfirebase.io/migrating-to-v22 Please use where() instead.

This is my code where the warning occurs -

const checkUsernameUnique = async (userName) => {
        try {
            const usersRef = collection(db, 'Users');
            const q = query(usersRef, where('username', '==', userName));
            const snapshot = await getDocs(q);
            return snapshot.empty; // ✅ Returns true if no user found
        } catch (error) {
            console.error('Error checking username uniqueness:', error);
            return false;
        }
    };

    const checkEmailUnique = async (email) => {
        try {
            const usersRef = collection(db, 'Users');
            const q = query(usersRef, where('email', '==', email));
            const snapshot = await getDocs(q);
            return snapshot.empty;
        } catch (error) {
            console.error('Error checking email uniqueness:', error);
            return false;
        }
    };

I have checked the instruction mentioned in new documentation but still getting the warning.

Which line of the lines you've shown generates that error? It seems to me that none of the lines shown here are using the deprecated API. Please edit the question to be clear. — Doug Stevenson
– Doug Stevenson, Commented Feb 14 at 19:43
I have already changed the code according to modular api but it is still showing the deprecation error. That's why I am asking what is wrong here. And the deprecation is in this part for sure because when I am commenting this lines it is not showing deprecation error. @DougStevenson — Muskan Verma
– Muskan Verma, Commented Feb 16 at 1:15
add this line at App.js globalThis.RNFB_SILENCE_MODULAR_DEPRECATION_WARNINGS = true; — Abhay dubey
– Abhay dubey, Commented Aug 6 at 12:22

Denis · Accepted Answer · 2025-05-05 17:01:27Z

This is how to solve the issue on the messaging module example.

Use this type of the import:

import { getMessaging, requestPermission, setBackgroundMessageHandler, onMessage, getToken, onNotificationOpenedApp, getInitialNotification, subscribeToTopic, hasPermission } from '@react-native-firebase/messaging';

Remove all messaging() calls and use imported methods directly. All of them (except getMessaging) require first additional argument: messaging instance.

Old code:

messaging().getInitialNotification().then(message => this.catchMessage(message));
var token = await messaging().getToken();

New code:

const messagingInstance = getMessaging();

getInitialNotification(messagingInstance).then(message => this.catchMessage(message));
var token = await getToken(messagingInstance);

Big example code is given here: https://github.com/invertase/react-native-firebase/issues/8282#issuecomment-2760400136

Bilal Sabugar · Accepted Answer · 2025-02-15 01:54:13Z

0

Correct Import for Firestore (Modular API)

Instead of:

import firestore from "@react-native-firebase/firestore";

Use:

import { getFirestore, collection, query, where, getDocs } from "firebase/firestore";

If you have this anywhere in your project, remove it and switch to the modular API.

Check Your Firebase Initialization:

import { initializeApp } from "firebase/app";
import { getFirestore, initializeFirestore } from "firebase/firestore";

const firebaseConfig = {
    apiKey: "",
    authDomain: "",
    projectId: "",
    storageBucket: "",
    messagingSenderId: "",
    appId: "",
    measurementId: "",
};


export const app = initializeApp(firebaseConfig);
const db = initializeFirestore(app, {
    experimentalForceLongPolling: true
});

export default db;

Update all dependencies:

npm install firebase@latest @react-native-firebase/app @react-native-firebase/firestore

Summary:

Remove any old namespaced imports
Use modular API imports
Ensure you're using getFirestore(app) in your Firebase setup
Update Firebase SDK versions and clear Metro cache

answered Feb 15 at 1:54

Bilal Sabugar

514 bronze badges

1 Comment

Muskan Verma Feb 16 at 1:16

Did all this already but it is still showing deprecation error.

MaartenDev · Accepted Answer · 2025-02-19 20:18:59Z

0

It should be

import { collection, query, where, getDocs, getFirestore } from '@react-native-firebase/firestore'

Checkout the docs: https://rnfirebase.io/migrating-to-v22

edited Feb 19 at 20:18

MaartenDev

5,8305 gold badges23 silver badges36 bronze badges

answered Feb 19 at 20:14

Osaro Imarhiagbe

1

Comments

eduardo Matos · Accepted Answer · 2025-07-25 19:48:23Z

I was getting the following warning when using Firebase Authentication in my React Native project, even after updating my code to follow the modular API:

This method is deprecated (as well as all React Native Firebase namespaced API) and will be removed in the next major release as part of move to match Firebase Web modular SDK API. Please see migration guide for more details: https://rnfirebase.io/migrating-to-v22

After checking the migration guide and trying several things, I finally resolved it by replacing:

import auth from '@react-native-firebase/auth';

with:

import { getAuth } from '@react-native-firebase/auth';
import { getApp } from '@react-native-firebase/app';

const app = getApp();
const auth = getAuth(app);

By doing this, the warning disappeared.

So if you're seeing this warning even when using modular Firestore code, double-check that none of your other Firebase imports (like auth) are still using the old namespaced syntax. That was the issue in my case.

Hope this helps someone else!

Collectives™ on Stack Overflow

Getting deprecation warning using firebase in react native

4 Answers 4

Comments

1 Comment

Comments

Comments

Hot Network Questions

Collectives™ on Stack Overflow

4 Answers 4

Comments

1 Comment

Comments

Comments

Related