ASK about FBSDKPackage #14816

Activity

1. asgvard commented on Jul 5, 2017

   

   asgvard

   on Jul 5, 2017

   More actions

   Hi,

   This issue is definitely related to "react-native-fbsdk" package and not to react-native itself. And it's documentation clearly says that you have to pass "mCallbackManager" into a FBSDKPackage constructor: Docs.
   That's exactly what the error says, "required: CallbackManager, found: no arguments".

   👍React with 👍9Reacted by Alec Breton, RafatAssaf, Ashkon, Maxime Vdb, Martin Richter, Ashwani Arya, Alan Chao, Mahmoud Felfel and Omorogieva Asemota Igbinosa

   😄React with 😄1Reacted by Rory Pickering

   🎉React with 🎉4Reacted by Alec Breton, Maxime Vdb, Alan Chao and Omorogieva Asemota Igbinosa
2. hramos

   closed this as completedon Jul 5, 2017
3. lwiecek commented on Jun 11, 2018

   

   lwiecek

   on Jun 11, 2018

   More actions

   Take a look at getPackages function in MainApplication. Make sure that new FBSDKPackage() is not on the list before new FBSDKPackage(mCallbackManager). In my case I had it listed twice and that was breaking the build.

   👍React with 👍1Reacted by Trent
4. react

   locked as resolved and limited conversation to collaborators on Jul 5, 2018
5. react-native-bot

   added

   Resolution: LockedThis issue was locked by the bot.This issue was locked by the bot.

   on Jul 18, 2018