Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Facebook login fails on some devices

I have implemented the Facebook login and it works fine on some devices/AVDs. My development device is a Gingerbread phone, but testing it with a 4.1.1 device, it simply does not log in. After pressing the facebook button, it shows a blank screen (trying to connect Facebook), and after 1-2 seconds it comes back to the home screen. Also, no errors are toasted or displayed in the Logcat. Oh, and the Facebook application is installed in the device... Any ideas?

UPDATE:

I enabled logging as suggested by Mark Venzke and using this procedure, and I got this warning (twice) on every login attempt (note: testing with a HTC One S phone):

07-05 20:14:50.582: W/PackageManager(605): Unable to load service info ResolveInfo{4171dbf0 com.htc.socialnetwork.facebook.remote.FacebookSyncService p=0 o=0 m=0x108000}

Note the com.htc.socialnetwork.facebook.remote.FacebookSyncService line, so is there any extra step needed for HTC devices?

Also, I'm attaching the code where the login is performed:

private void onSessionStateChange(Session session, SessionState state, Exception exception) {
    if (isResumed) {
        FragmentManager manager = getSupportFragmentManager();
        int backStackSize = manager.getBackStackEntryCount();
        for (int i = 0; i < backStackSize; i++) {
            manager.popBackStack();
        }
        com.facebook.Settings.addLoggingBehavior(LoggingBehavior.REQUESTS);
        if (state.isOpened()) {

            Bundle params = new Bundle();
            params.putString("fields", "id");
            params.putString("limit", "1");             
            Request request = new Request(Session.getActiveSession(), "me", params, HttpMethod.GET, new Callback()
            {

                @Override
                public void onCompleted(Response response)
                {
                    if (response != null)
                    {
                        Log.d("AuthGraphResponse", response.toString());
                        long id;
                        try {
                            id = response.getGraphObject().getInnerJSONObject().getLong("id");
                            app.setFacebookId(id);
                            Log.d("UserID", Long.valueOf(id).toString());
                        } catch (JSONException e) {
                            e.printStackTrace();
                        }
                    }
                }
            });

            RequestAsyncTask task = new RequestAsyncTask(request);
            task.execute();

            showFragment(AUTH, false);
        } else if (state.isClosed()) {
            showFragment(UNAUTH, false);
        }
    }
}

UPDATE 2:

Is it possible that HTC renames the package name of the default Facebook application in all the devices (or some of them, whatever) to com.htc.socialnetwork.facebook (instead of com.facebook.katana) and it leads to this conflict? I don't really think that uninstalling the default app and installing Facebook from Google Play is an acceptable solution (also, I think default apps cannot be uninstalled).

UPDATE 3:

Not solved yet. 19 hours to award the 100 reputation bounty!

UPDATE 4:

Another interesting line of the LogCat:

07-15 10:55:51.718: E/chromium(30475): external/chromium/net/disk_cache/stat_hub.cc:216: [0715/105551:ERROR:stat_hub.cc(216)] StatHub::Init - App com.facebook.katana isn't supported.
like image 872
Dhanesh Budhrani Avatar asked Jun 24 '13 14:06

Dhanesh Budhrani


4 Answers

There is certainly a conflict between your stock app and the SDK. So if you don't want to uninnstall the stock HTC app and still use the SDK 3.0 I think your best bet without modying the source code of the sdk would be to disable SSO and login only through webview.

This can easily be done by adding the SessionLoginBehavior.SUPRESS_SSO everytime you try to open a new session. Here is a sample I changed from the SessionLoginSample (LoginUsingActivityActivity) from the Facebook SDK to show you what to do :

@Override
public void onCreate(Bundle savedInstanceState) {
    ...
    Session session = Session.getActiveSession();
    if (session == null) {
        if (savedInstanceState != null) {
            session = Session.restoreSession(this, null, statusCallback, savedInstanceState);
        }
        if (session == null) {
            session = new Session(this);
        }
        Session.setActiveSession(session);

        //add the check, for if session is opened
        if (session.getState().equals(SessionState.CREATED_TOKEN_LOADED) || !session.getState().isOpened()) {
            //Add the suppress SSO behavior to force webview auth dialog to popup
            session.openForRead(new Session.OpenRequest(this).setCallback(statusCallback).setLoginBehavior(SessionLoginBehavior.SUPPRESS_SSO));
        }
    }
  ...
}
//then put your code in the statusCallback method or keep it in the session state change listener

Otherwise if you don't mind changing the facebook sdk code, you should check this out

like image 78
Gomino Avatar answered Sep 21 '22 17:09

Gomino


Shirley Facebook login is not broken on all 4.1.1 devices, so it is something with your implementation.

Are you sure the Key Hash is the same on that device as what you have configured on developer.facebook.com? If you used a different dev key, or it was installed by a third-party store, it's possible the key hashes don't match.

Turn on debug logging in the Facebook SDK source code and rebuild it. It is generally off by default for security reasons. Depending on your version of the SDK, it may be in Util.java or some other location, and may be a variable called 'ENABLE_LOG'.

like image 37
Mike Venzke Avatar answered Sep 20 '22 17:09

Mike Venzke


I think facebook login error mostly occur so to solve this issue you follow there tutorial step by step again with patience.

Other wise its very difficult to solve your problem here. So you can refer this link.

http://developers.facebook.com/android/

I hope you will success.

like image 30
Yogendra Avatar answered Sep 22 '22 17:09

Yogendra


There isn't enough info in your question. so, I'm making a few guesses here.

1)First look into Mike Venzke's answer.

2) If this doesn't work then try this: You need to sign in on you device using SSO (Single Sign On). So here are the steps you can take.

delete the build. reinstall it. and when asked for permissions from your device, allow them.

If you aren't taken back to your app then you need to add these to your manifest file:

<activity
        android:name="com.facebook.LoginActivity"
        android:label="@string/app_name" >
    </activity>
<meta-data android:value="@string/app_id" android:name="com.facebook.sdk.ApplicationId"/>

where app_name and app_id are your respective app Id and app name on your Facebook app page.

Have you added these btw?

you need these permission as well

<uses-permission android:name="android.permission.WAKE_LOCK"/>
<uses-permission android:name="android.permission.GET_ACCOUNTS"/>
<uses-permission android:name="android.permission.INTERNET" />
<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />

if you post some more info I might be guess the issue.

like image 21
Azhar Yousuf Avatar answered Sep 19 '22 17:09

Azhar Yousuf