-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Conflict with Nearby library #14210
Comments
I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight. |
Also see: google/nearby#1916 |
Looks like nearby is using an older version of boringssl that is not compatible with Firebase 11.x both because of the version and Firebase's transition to using a binary by default. |
Ticket filed: google/nearby#3100 |
I am also facing the similar issue with Firebase version 11.2.0 it seems both Firebase and Nearby depends on common library which relates to a version conflict between BoringSSL-SwiftNPM and gRPC-binary. |
Description
Our project already uses Firebase, added via SPM.
However we now want to add the Nearby library via SPM and are running into conflicts when trying to resolve the package dependencies.
Removing Firebase allows us to successfully add Nearby, but having them both in the project causes conflict problems:
Reproducing the issue
Steps 2. and 3. can happen in either order (it still fails).
Firebase SDK Version
11.6.0
Xcode Version
16.1
Installation Method
Swift Package Manager
Firebase Product(s)
Crashlytics
Targeted Platforms
iOS
Relevant Log Output
No response
If using Swift Package Manager, the project's Package.resolved
Expand
Package.resolved
snippetReplace this line with the contents of your Package.resolved.
If using CocoaPods, the project's Podfile.lock
Expand
Podfile.lock
snippetReplace this line with the contents of your Podfile.lock!
The text was updated successfully, but these errors were encountered: