Skip to content
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

ios build failed (Linker Command Fail) #48

Open
nertilzhuri opened this issue Aug 8, 2017 · 5 comments
Open

ios build failed (Linker Command Fail) #48

nertilzhuri opened this issue Aug 8, 2017 · 5 comments

Comments

@nertilzhuri
Copy link

First of all thank you for this great library.

I am having a hard time configuring it due to build failures on iOS:
I have done everything as readme suggests (react-native link, linking libraries in xcode...), and whenever I try to build (either xcode or terminal) I get the following error:

Apple Match-O Linker Error: Linker command failed with exit code 1
social-share-problem

I also want to mention that the files inside the Libraries folder are missing (even after reinstalling a couple of times) as you can see on the image below. This problem was mentioned also in issue #22
social-share-problem-2

I have tried the following:

  • Cleaning the project and rebuilding
  • Removing the files and re-linking
  • Reinstalling the library

System Information and Development Environment
react: 16.0.0-alpha.12
react-native: 0.45.1
Simulator: iphone6

I am looking forward for any solution or any way I can be helpful. Thank you in advance.

@shtsht
Copy link

shtsht commented Sep 3, 2017

I faced same time.
Removing lRCTWebSocketDebugger.a in TARGETS-> {YOUR PROJECT}->Build Phases->Link Binary With Libraries solved this issue.
Hope this will help you!

@LeoTianJob
Copy link

Thanks @shtsht , It also works for me.

@imchathu87
Copy link

wow it works , But Why ?

@doefler
Copy link
Owner

doefler commented May 17, 2018

Thank you, everyone, for helping out 😄
Is this an edge case or something that we should include into the README as a setup step?

@imchathu87
Copy link

@doefler nop , I think its better you put a new release by fixing that :) , bcs its a issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants