Facebook SDK FB.Init fails

So far I have followed this youtube tutorial but have been unable to gwt FB.Init to work.

The only thing that was different is versions:
Unity version 5.2.1f1, Facebook SDK 7.1.0

How to troubleshoot this issue?

 

A few things have changed. https://developers.facebook.com/docs/unity/change-log

• FB.Login has been split into FB.LoginWithReadPermissions and FB.LoginWithPublishPermissions
• IResult replaces FBResult

I used:

Code (CSharp):

1. public void FBLogin()
2.     {
3.         List<string> perms = new List<string>() { "public_profile, email", "user_friends" };
4.         FB.LogInWithReadPermissions(perms, AuthCallBack);
5.     }
6. }
7.  
8. void AuthCallBack(ILoginResult result)
9.     {
10.         if (FB.IsLoggedIn)
11.         {
12.             // AccessToken class will have session details
13.             var aToken = Facebook.Unity.AccessToken.CurrentAccessToken;
14.             // Print current access token's User ID
15.             Debug.Log(aToken.UserId);
16.             // Print current access token's granted permissions
17.             foreach (string perm in aToken.Permissions) {
18.                 Debug.Log(perm);
19.             }
20.             DealWithFBMenus(true);
21.         } else {
22.             Debug.Log("User cancelled login");
23.             DealWithFBMenus(false);
24.         }
25.     }

 

Yes I noticed these changes but I haven't got that far since I'm already experiencing issues in fb.init.

 

This is what I have currently, but always getting Debug.Log("Failed to Initialize the Facebook SDK");
Funny thing is that this works in example scene which comes with the FB SDK

Code (CSharp):

1.    
2. void Awake()
3.     {
4.         if (!FB.IsInitialized)
5.         {
6.             // Initialize the Facebook SDK
7.             FB.Init(this.InitCallback, this.OnHideUnity);
8.             Debug.Log("FBInit is called with appID:" + FB.AppId);
9.         }
10.         else
11.         {
12.             // Already initialized, signal an app activation App Event
13.             FB.ActivateApp();
14.         }
15.     }
16.  
17.     private void InitCallback()
18.     {
19.         if (FB.IsInitialized)
20.         {
21.             // Signal an app activation App Event
22.             FB.ActivateApp();
23.             // Continue with Facebook SDK
24.             // ...
25.             var perms = new List<string>() { "public_profile", "email", "user_friends" };
26.             FB.LogInWithReadPermissions(perms, AuthCallback);
27.         }
28.         else
29.         {
30.             Debug.Log("Failed to Initialize the Facebook SDK");
31.         }
32.     }
33.  
34.     private void OnHideUnity(bool isGameShown)
35.     {
36.         if (!isGameShown)
37.         {
38.             // Pause the game - we will need to hide
39.             Time.timeScale = 0;
40.         }
41.         else
42.         {
43.             // Resume the game - we're getting focus again
44.             Time.timeScale = 1;
45.         }
46.     }

 

I've got the same problem with FB.Init(). If You simply do the things that Facebook provides in example docs it just throughs "Failed to Initialize the Facebook SDK" so it goes to InitCallback function to else block...
Couldn't find any solution yet. If someone reaches any results, please help the others

 

I've got the same problem. Did you solved this problem ?

 

Try this

from facebook bugs site:

in the FacebookGameObject " this.Initialized = true" is call after the call back ".OnInitComplete". so if (FB.IsInitialized) always = false

public void OnInitComplete(string message)
{
this.Facebook.OnInitComplete(message);
this.Initialized = true; }

Should be

public void OnInitComplete(string message)
{ this.Initialized = true;
this.Facebook.OnInitComplete(message);
}

 

@IlkoIliev thanks that did the trick and it is working now as expected

 

I had the same issue, but realised it was because on recently updating Unity & Facebook SDK I had lost my App ID info in the FB Settings...

 

Today I updated to latest Facebook SDK 7.2.0 and noticed that this issue is now fixed in sdk as well.