-
Notifications
You must be signed in to change notification settings - Fork 906
Conversation
The change already exists in 0.39, maybe we should merge it now? |
The change is only part of 0.40 according to tags on facebook/react-native@e1577df. There was a bit of discussion around it and seems like the change to header paths won't be needed anymore but all imports will still need to be updated. Will update this PR once this is settled. Also take note that this change is NOT backwards compatible sadly so we have to depend on RN 0.40+ after merging this. |
@janicduplessis I'm trying to migrate to 0.39.2, but I can't because this hasn't been merged yet. Any plans on merging it soon? Thanks! |
@janicduplessis updated the pull request - view changes |
@jpapillon Are you sure this is needed for 0.39? According to the tags on the github commit this is only part of 0.40 facebook/react-native@e1577df |
We're facing same issue. Unable to run current version on 0.39 but Your branch works on 0.39. Gave it 2h to try to understand it. Makes no sense at all. 😳 |
@janicduplessis 0.39.2, yes. Works fine on 0.38! |
RnFbSDK is not working on 0.39.2. |
Hi, RN 0.40.0 has been released. Any plans to merge this and push out a new distro? |
@dzhuowen Please can someone merge this? Thanks! |
Guys do you experience the same thing? AccessToken.getCurrentAccessToken() returns null after application restart, even tho it returns valid access token after a successful login. |
fwiw, installing the package from @janicduplessis's fork works for me. i'm only using the login functionality but in principle everything else should work as well as there haven't been any changes since the 0.4.0 release and all this PR does is update the import statements to work with RN 0.40.0. |
Did you use LoginManager? And than check AccessToken to check for its existence on application boot. Though react-native-facebook-login with its' default login button also resets to Login state after app restart. Would so much appreciate if you can help. |
+1 please merge |
AccessToken is null after app restart - thats the bug of Facebook SDK 4.18, switched to 4.17 and everything works like a charm :) Hope that helps everyone else who came to the same issue. |
Thanks for the PR! We'll release a new version soon. |
For the impatient, you can install the latest version with this fix from github right now with:
This will write to your
(you'll probably want to I also had to manually run |
Thank you @christiangenco! Huge help. |
Thanks @dzhuowen! Can't wait for the new release! :) |
Thanks for the PR! |
The new version should be published to npm later this week. |
I have FBSDKCoreKit/FBSDKCoreKit.h file not found error and spent several hours trying to solve it, but can't understand whats going wrong(( Any ideas? react-native 0.40 |
Try on of the following:
Hopefully it helps |
@Amurmurmur, now I have Undefined symbols for architecture x86_64: God damn, I can't build fbsdk a couple of days!(( |
RCTFBSDKInitializer.m:22:9: fatal error: 'FBSDKCoreKit/FBSDKCoreKit.h' file not found "react-native": "0.41.2", Any Idea? |
SOLVED! 1.- react-native uninstall react-native-fbsdk |
Solution 2: |
Hello there! |
facebook/react-native@e1577df moves header imports to
<React/*>
. This updates header include path and all imports so build works against react master (soon to be version 0.40.0).TODO: Fix / update sample when 0.40 is out.