[🐛] Property 'firebase' doesn't exist 😱

[birdofpreyru]

Issue

The latest v21.11.0 version of the lib, after upgrading to its new, modular API, inside the database lib module:

I also see, there is the same error just above, at the line 112 of that file.

---

Project Files

Javascript

Click To Expand

package.json:

# N/A

firebase.json for react-native-firebase v6:

# N/A

iOS

Click To Expand

ios/Podfile:

• I'm not using Pods
• I'm using Pods and my Podfile looks like:

# N/A

AppDelegate.m:

// N/A

---

Android

Click To Expand

Have you converted to AndroidX?

• my application is an AndroidX application?
• I am using android/gradle.settings jetifier=true for Android compatibility?
• I am using the NPM package jetifier for react-native compatibility?

android/build.gradle:

// N/A

android/app/build.gradle:

// N/A

android/settings.gradle:

// N/A

MainApplication.java:

// N/A

AndroidManifest.xml:

<!-- N/A -->

---

Environment

Click To Expand

react-native info output:

 OUTPUT GOES HERE

• Platform that you're experiencing the issue on:
  • iOS
  • Android
  • iOS but have not tested behavior on Android
  • Android but have not tested behavior on iOS
  • Both
• react-native-firebase version you're using that has this issue:
  • e.g. 5.4.3
• Firebase module(s) you're using that has the issue:
  • e.g. Instance ID
• Are you using TypeScript?
  • Y/N & VERSION

---

• 👉 Check out React Native Firebase and Invertase on Twitter for updates on the library.

[MichaelVerdon]

I have released a PR that should fix this, thanks for your ticket.

[Nantris]

We're still seeing this in @react-native-firebase/database@21.12.0

When calling serverTimestamp we get the error: "Property 'firebase' doesn't exist"

It worked fine for us in 21.7.1.

Thanks for your work on this @MichaelVerdon - I wonder if you have any thoughts about an underlying cause here?

---

Tested on physical Android 14 device running React Native 0.76.7.

[Nantris]

@birdofpreyru I wonder if this is fixed for you? It would seem strange that the PR would fix increment but not fix (or possibly even break?) serverTimeStamp.

[birdofpreyru]

@Nantris I don’t know, when I bumped into the problem, I worked it around by taking increment from the old, default export, and never arrived to try its new export again 😅

[Nantris]

Thanks for your reply!

Just wanted to update that 21.9.x also seems to have this issue. 21.7.x didn't have this problem. I haven't tested 21.8.0.

@mikehardy I think something is wrong here beyond what #8377 tried to addressed.

---

Edit: Actually it seems like 21.7.x may have had the problem? I'll have to check tomorrow.

[mikehardy]

Reopening to make sure we take a look (note that we have not released a version with the PR yet, so it is possible that it is fixed, just not released yet...)

[Nantris]

Ah I see! My mistake. It's very possible this is fixed then. I'll keep an eye out for the next release. Thanks so much!

[Nantris]

Seems like 21.7.4 is bad but 21.7.1 is good, so I guess this commit is the introduction of the problem: 79da98b

Just wanted to update on my findings, though it may already be known and I'm not sure it matters anyway since this may be fixed.

[mikehardy]

The new version of react-native-firebase with most of the fixes is out - there are still some fixes to work through but...hopefully this fixes up the firebase issues, if not will do a quick follow-on