-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[🐛] No Firebase App '[DEFAULT]' has been created - call firebase.initializeApp() #7581
Comments
@mikehardy please help |
Very strange. It appears you have a react-native that is modern enough (0.73.2 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 |
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 |
@mikehardy It works fine with new architecture enabled. But once the bridgeless mode is enabled along with new architecture it starts giving the error. |
Oh, as far as I know this package does not support New Architecture at all. It has not been converted.
https://rnfirebase.io/#altering-cocoapods-to-use-frameworks Because New Architecture has historically not been compatible with 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 |
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.. |
|
(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. |
Issue
It was working fine before enabling bridgeless mode in react-native version 0.73.2. But after enabling the bridgeless mode it has started to give this error.
(NOBRIDGE) ERROR Error: No Firebase App '[DEFAULT]' has been created - call firebase.initializeApp()
(NOBRIDGE) LOG Running "singlecustomerapp" with {"rootTag":1,"initialProps":null,"fabric":true}
(NOBRIDGE) ERROR Invariant Violation: "singlecustomerapp" has not been registered. This can happen if:
AppRegistry.registerComponent
wasn't called.Project Files
Javascript
Click To Expand
package.json
:firebase.json
for react-native-firebase v6:iOS
Click To Expand
ios/Podfile
:AppDelegate.m
:Android
Click To Expand
Have you converted to AndroidX?
android/gradle.settings
jetifier=true
for Android compatibility?jetifier
for react-native compatibility?android/build.gradle
:android/app/build.gradle
:android/settings.gradle
:MainApplication.java
:AndroidManifest.xml
:Environment
Click To Expand
react-native info
output:react-native-firebase
version you're using that has this issue:18.7.3
TypeScript
?Y
&5.3.3
React Native Firebase
andInvertase
on Twitter for updates on the library.The text was updated successfully, but these errors were encountered: