Add support for connecting to Auth emulator
In the official docs, the Firebase Web client can connect to the local Auth emulator using firebase.auth().useEmulator(<url>);. Link here: https://firebase.google.com/docs/emulator-suite/connect_auth#web It would be awesome if this could be translated to React Native as well, similar to functions().useFunctionsEmulator()
Render custom In App Messaging(FIAM) using react-native component
Customizing the In App Messaging display with @react-native-firebase/in-app-messaging is nearly impossible, currently our workaround is just add native FIAM without @react-native-firebase/in-app-messaging and modify the native code to customize the display, it's painful for company which is using react-native for app development. It will be wonderful if we can just render custom In App Messaging display using react-native component.
Support Firestore DataConverter (withConverter)
The Firebase SDK has exposed a withConverter() method, on a Document/CollectionReference and Query, since 7.6.0 ( https://firebase.google.com/support/release-notes/js#cloud-firestore_15 ) It would be great to see that exposed in react-native-firebase. API Reference here: https://firebase.google.com/docs/reference/js/firebase.firestore.FirestoreDataConverter
New Native Ad Format
RNfirebase only supports Native Express Ads which will be deprecated soon. Is there a plan to add the new native format?
Adaptive Banner Ads
Is there currently any way to support Adaptive Banners https://developers.google.com/admob/ios/banner/adaptive
On dismiss event for fcm notification
it would be nice if you could add the onDismiss event as well as the onNotificationOpenedApp, I was trying to implement it myself but I found it too difficult
Migrate to TypeScript
I'm using the v6 and TS typings are a bit broken. I think migrating the source code to TypeScript could help in many aspects: Immediately catch type errors; More signal, less noise (because a lot of duck typing won't be needed anymore); Self-documenting nature of static typing will make it a lot easier for other people to contribute; Less chances of accidentally breaking things during refactorings. Those are only some of the benefits. There are other less important ones like better IDE experience and not needing to keep separate, unsynced d.ts files. If you think it's a good idea, I may be able to help with PRs.
Version 5 notification is very useful, when you will integrate this inside version 6?
ML Kit On-Device
In June Google decided to split the ML Kit's on-device functions to a separate SDK, which means the firebase functions for it won't get any updates anymore and probably won't work at some point. Do you have any plans of integrating the standalone ML Kit as well for keeping the on-deivce operations functioning?
Use latest Firebase Crashlytics SDK?
I was wondering when do you plan to integrate the latest Firebase Crashlytics SDK? I know it's still in beta, but considering Fabric will be deprecated and shutting down March 31, 2020, we were about integrate it from here. But in the manual steps for Android I still see steps, related to Fabric. Thanks in advance.