Closed mikehardy closed 7 months ago
Worth noting that temporarily both FlutterFire and react-native-firebase have this workaround / direct dependency in their firestore podspecs so this is not an urgent issue for the two largest potential consumers of this repository
But if you depend on this repository directly in another form, you quite likely will need to add the nanopb dependency as described in code snippet above until the issue is resolved
Hi, I have similar issue with nativesript/angular. Is it a fix I can apply in my project or hat it to be done by nativescript?
1- FirebaseFirestore requires nanopb 2- Upstream, FirebaseCore used to depend on FirebaseCoreDiagnostics, which transitively gave us a dependency on nanopb 3- FirebaseCoreDiagnostics was removed from FirebaseCore dependency chain for v10+ of firebase-ios-sdk meaning we no longer have this "free" transitive dependency
Temporary resolution is to add a dependency on nanopb with correct version constraints to consumers of this dependency:
https://github.com/firebase/firebase-ios-sdk/blob/bb4c6382cd52e805a721f981c1838eaa815f6dbd/FirebaseFirestore.podspec#L105
More complete fix will involve adding something similar to the leveldb dependency here, where we attempt to detect if leveldb exists by examining the other deps to see if one of them is in the list above, or allowing consumer to specify it directly, or...something else if there is a better solution