[📚] Messaging - Show Modular Example instead of Namespaced in documentation

[estani]

Documentation Feedback

Please describe your documentation issue or suggested improvement in detail here and provide links to any pre-existing/relevant documentation and screenshots if necessary:

In https://rnfirebase.io/messaging/usage#ios---requesting-permissions

The "deprecated" usage is documented.
I've tried to use the modular "recommended" one, but without success.
I've changed it to:

import { hasPermission, requestPermission } from "@react-native-firebase/messaging";
// changed from messaging.hasPermission();
let permission = await hasPermission(/* Messaging instance expected */);
// ...
//changed from messaging.requestPermission()
permission = await requestPermission(
 /* messaging: Messaging, iosPermissions?: FirebaseMessagingTypes.IOSPermissions */)
);

Or is it ment to not be used at all?

const firebaseApp = getApp();
const messaging = getMessaging(firebaseApp);
// But... Error: No Firebase App '[DEFAULT]' has been created - call firebase.initializeApp()

It is not clear to me what should be used now, and where the messaging object should come from. Please update the docs.

[MichaelVerdon]

Hi there, which function is calling the deprecation warning? Could you please paste the console logs here?

[estani]

 WARN  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 `getApp()` instead. [Component Stack]

Sent apparently from

react-native-firebase/packages/app/lib/common/index.js

Line 695 in 7eaaf18

for (let i = 0; i < args.length; i++) {

Though I couldn't find where "exactly" it is thrown...

[MichaelVerdon]

We generally advise people to look at the JS Documentation as we aim to match it as much as possible here, to solve your issue check out here please https://firebase.google.com/docs/cloud-messaging/js/client and we should get the documentation updated here soon as-well. Let me know how this goes.

[estani]

Ok, I'll check it. I was already trying something similar, while looking into the code... though it feels strange, as this is completely different to the react-native-firebase approach, afaict. It means, e.i., that the expo config does not work directly anymore, since the configuration will be needed to be passed manually to the initializeApp method, and a singleton need also to be maintained by the application itself, in order to be able to call the methods. It kind of feel, that precisely that was the intention of react-native-firebase in the first place. It feels kind of redundant now.