[🐛] Project wont compile with use_frameworks! :linkage => :static about react-native-firebase HOT 6 CLOSED

react native version v0.71.17

That's a bit worrisome, you should make sure react-native is also up to date before logging build issues as it is an integral part of the build system as well

Are this errors or (as in the text you quoted a "Note" ? That is, does your project still build?

Finally, for build testing I use this rig and I don't see this, so I'm not sure what the difference is, but my demonstration is fully reproducible and automated based on our documentation, and it appears to work without these issues - so I'm not sure what the difference is but I'm inclined to think it's in the project somewhere ? https://github.com/mikehardy/rnfbdemo/blob/main/make-demo.sh

from react-native-firebase.

@mikehardy v0.71.17 is up to date. it was released 28 feb 2024. Is there a new minimum version for latest Firebase?

we had a missing dependancy in one of pods, fixing that resolved our issue. Hard to tell what the issue was with all the
"Implicit dependency" noise

from react-native-firebase.

Glad your issue is fixed!

v0.71.17 is up to date. it was released 28 feb 2024. Is there a new minimum version for latest Firebase?

It's not up to date, 0.73.6 is current I think? You're version is just a minimum watch on an old version.
In general we follow react-native support rules which is current and 2 old versions so we try to make things work but it is always more efficient for troubleshooting to be actually current, which is why I mentioned it. Moot point this time though!

from react-native-firebase.

@mikehardy do you have a link to the "react-native support rules"?

Latest react native release is 0.73. 2 old versions back would be last two major releases 0.72 and 0.71?

Or are you saying you only support the latest native version only and last 2 minor releases back?

from react-native-firebase.

I apologize I cannot find the policy document from upstream easily while mobile but the versions document dies clearly indicate what gets support and what does not https://reactnative.dev/versions

We (I) strive to support as far back as possible but there are technical limitations frequently

To be clear my point is about efficiency

New versions have fixes. Very frequently the fixes are build related (sometimes feels like all I do!). So troubleshooting old versions frequently results in "oh we already fixed that, upgrade...". Inefficient. Just something to think about when contemplating spending time pursuing any issue but especially build issues

from react-native-firebase.

Also, it's 0.73.6.

Pulled it from memory before but just verified. Ref https://www.npmjs.com/package/react-native?activeTab=versions

Again, moot point here, but precision has value, as do citations - cheers

from react-native-firebase.