-
Notifications
You must be signed in to change notification settings - Fork 24.3k
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
could not link react-native-fbsdk #14670
Comments
+1 |
1 similar comment
+1 |
delete package-lock.json and redo npm install, the npm 5 is broken, you either always have to delete package-lock.json and redo npm install or just use npm 4 |
I followed the steps and am still getting the error |
I ran Finally I updated my react-natvie-fbsdk by running |
npm install --save react-native-fbsdk@0.6.0 but if you forget update to latest, android will get a trouble in build.gradle compile('com.facebook.android:facebook-android-sdk:4.+') |
@manggit I can run that command ok, but for every subsequent |
@Charles-LMQ your suggestion worked. It didn't work at first so I had to upgrade from npm 3.3.9 to 5.0.4 then went down to 0.6.0 for fbsdk. dependencies": { @thienpow - this has nothing to do with package-lock.json from what i can tell. Removed it multiple times and nada. |
Also hitting this. Installing 0.6.0 works however. |
looks like the issue is stuck at this PR |
npm install --save react-native-fbsdk@0.6.0 comment then react-native link every thing will be fine |
+1 React-Native: 0.47.2 This works for iOS but how have you got it to run on Android? I keep running into:
|
+1 the workaround involving installing 0.6.0, linking, update to 0.6.1 works but only temporary. each time I need to relink I have to do it again, I think this issue should still be open. |
This should absolutely still be open. 0.6.1 does not work with iOS. This makes it necessary to split the project into iOS/Android with two different I've tested with a completely clean build at 0.47.2 just for the FBSDK to no avail. You'd have to down-version RN to get 0.6.1 to work but I'm not sure how far down. I've seen reports of 0.45 being ok. |
Its works with RN 0.48.1 and FB SDK 0.6.0
|
Right, 0.6.0 works with 0.47.2 as well, 0.6.1 does not. And 0.6.0 does not work with Android/RN 0.47.2. Android requires 0.6.1 |
Does anybody have a combinaison of versions working on both android and ios ? |
RN 0.48.1 & FBSDK 0.6.0 ... working both android & ios |
Just received an update on my bug report. Haven't gotten a chance to try this yet but if someone wants to give it a shot... "While we work on a fix, as a workaround, can you try deleting the file |
There is a PR fixing this issue still unmerged: facebookarchive/react-native-fbsdk#349 (as mentioned above by @raduflp). |
For the past hours, I am trying unsuccessfully to connect the Facebook SDK in React Native.
I am running Windows, Android Studio 2.3.1. ( C:\Users\nicoara\Desktop\demoapp1>react-native link react-native-fbsdk and then still, it does not recognize if I add the following line in MainApplication.java: 'import com.facebook.FacebookSdk' How to proceed? |
wtf it's been a whole day trying installing this framework on osx for ios without success... my config: on android is working. please some advice, as the docs on FB developer website seems to be broken or at least not working for me. |
I upgraded react-native-fbsdk to 0.7.0, now IOS stopped working, I see just white screen, when trying to log in/sign up via Facebook. I was trying to downgrade react-native-fbsdk back to 0.6.0, 0.6.2, but this white empty screen is still there. Android works fine. Any advice how is possible to fix that? RN: 0.47.2 |
I'm not sure if this is a bug with rnpm. I was trying to run
react-native link react-native-fbsdk
and got this error:
rnpm-install info Android module react-native-fbsdk is already linked
rnpm-install info Linking react-native-fbsdk ios dependency
rnpm-install ERR! Something went wrong while linking. Error: Expected "/*", "//", or "{" but "<" found.
Please file an issue here: https://github.com/facebook/react-native/issues
Expected "/*", "//", or "{" but "<" found.
The text was updated successfully, but these errors were encountered: