-
Notifications
You must be signed in to change notification settings - Fork 181
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
clang: error: linker command failed with exit code 1 (use -v to see invocation) #89
Comments
nanopb was introduced in Firebase iOS Version 4.0.4. You can set your dependency to |
Hi @zgosalvez I set Firebase
But it doesn't help me |
@zgosalvez I see this in the terminal
|
@alexsanderkhitev, I only altered the 'Firebase' dependency. Paste this as is, as this will tell CocoaPods to install the specific version, not a variant of it.
|
@zgosalvez thank you so much. Interesting situation with subsequent updates, it turns out if you use Geofire it will not work to update Firebase on versions higher than 4.0.3 |
You can fix this by adding nanopb as a library search path for geofire in the post_install phase.
|
Note that we're also planning on switching Firebase 4.x dependencies to the |
I get the same error: clang: error: linker command failed with exit code 1 (use -v to see invocation) But none of these solutions worked for me. |
In addition to coli88's answer, you will also need to add leveldb-library as a framework search path:
|
Closing since this has staled. If you're still having build issues, please open a new issue and I'll address it. |
Hello! I'm using GeoFire (2.0.0) in the Swift project, after today's update pods when the project is going to Xcode shows clang: error: linker command failed with exit code 1 (use -v to see invocation) in the Geofire framework. Tell me, how can I fix this?
I install Geofire via Cocaopods as follows
pod 'GeoFire', :git => 'https://github.com/firebase/geofire-objc.git'
Update:
ld: framework not found nanopb
clang: error: linker command failed with exit code 1 (use -v to see invocation)
The text was updated successfully, but these errors were encountered: