[🐛] No Firebase App '[DEFAULT]' has been created - call firebase.initializeApp() about react-native-firebase HOT 11 CLOSED

Oh, as far as I know this package does not support New Architecture at all. It has not been converted.

New Architecture: Fabric is not compatible with use_frameworks!. Community support to help fix use_frameworks support for New Architecture is welcome!

https://rnfirebase.io/#altering-cocoapods-to-use-frameworks

Because New Architecture has historically not been compatible with use_frameworks! and that is a strict requirement of our underlying firebase-ios-sdk, there has been no attempt to make react-native-firebase compatible with new architecture yet

I recognize that this has just recently changed upstream (in just the last couple of months...use_frameworks is supposed to work now) so this will be an area of work in the future.

Until there is a release (noted in our changelog) where new architecture support is added and tested working I would have no expectation new architecture works

from react-native-firebase.

@NobodyButMe-Haiya

• your comment does not seem to be related to any of the context in this issue?
• "the developer" --> it is open source, you are the developer. I help maintain this repo but I'm just a developer alongside you. In open source if you must have things work you must invest the time to have things work, otherwise you must wait
• fully automated start-to-finish working react-native-firebase integration demonstration: https://github.com/mikehardy/rnfbdemo/blob/main/make-demo.sh

from react-native-firebase.

@mikehardy please help

from react-native-firebase.

Very strange.

It appears you have a react-native that is modern enough (0.73.2 is the current release...)
It appears you are using the most current up to date google services plugin (4.4.0 is the current release...)

This should be working.

There is a slight chance that backing the google services plugin down to 4.3.15 could make it work for you but I will be very surprised by that - it would be a data point that goes against our current hypothesis in this area

from react-native-firebase.

I use this script to verify everything is working together, and last I checked (a week or so ago...) everything was working fine.

https://github.com/mikehardy/rnfbdemo/blob/main/make-demo.sh

I will re-run it now but I expect everything will be working, and if so then I'm not sure what is different between your project and that script, but I would suggest a read of the script (it has comments explaining what it does...) so that hopefully the difference becomes apparent

from react-native-firebase.

@mikehardy It works fine with new architecture enabled. But once the bridgeless mode is enabled along with new architecture it starts giving the error.

from react-native-firebase.

I recognize your specific use case isn't handled yet (new architecture + bridgeless mode) but despite wishing it worked even myself, this is expected behavior so I'm going to close this.

If the module doesn't work using old architecture (or, I suppose new architecture with the new bridge for non-converted modules like this one...) then we can reopen of course

from react-native-firebase.

I recognize your specific use case isn't handled yet (new architecture + bridgeless mode) but despite wishing it worked even myself, this is expected behavior so I'm going to close this.

If the module doesn't work using old architecture (or, I suppose new architecture with the new bridge for non-converted modules like this one...) then we can reopen of course

yep it works with new architecture only or old architecture only but with bridgeless enabeld and new architecture enabled it gives the error message.

from react-native-firebase.

I recognize your specific use case isn't handled yet (new architecture + bridgeless mode) but despite wishing it worked even myself, this is expected behavior so I'm going to close this.
If the module doesn't work using old architecture (or, I suppose new architecture with the new bridge for non-converted modules like this one...) then we can reopen of course

yep it works with new architecture only or old architecture only but with bridgeless enabeld and new architecture enabled it gives the error message.

any sample which work ? . or you try work out of da box ? we use the same version 0.73.2 and get above title message. We just hope get update from the developer in few weeks.. hope..

from react-native-firebase.

I got the same error in ios.First time i put [FIRApp configure] after this line [RNSplashScreen show],then I got the error " No Firebase App '[DEFAULT]' has been created - call firebase.initializeApp() ". But then i add [FIRApp configure] before the [RNSplashScreen show], everything is ok!

So i guess RNSplashScreen show affect it's initialization.

from react-native-firebase.

(Maybe) When this PR is merged, it will address the issue related to bridgeless mode being enabled by default in react-native 0.74.0.

#7688

from react-native-firebase.