Facebook SDK 4.0.1 login NPE
I get NPE when I try to log into facebook on Kitkat, works fine on Lollipop MR1. I have tried 4.0.0 and 4.0.1
My login:
LoginManager.getInstance().logInWithReadPermissions(this, Arrays.asList(READ_PERMISSIONS));
crash
java.lang.RuntimeException: Unable to start activity ComponentInfo{lt.segfoltas.psm/com.facebook.FacebookActivity}: java.lang.NullPointerException
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2198)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2257)
at android.app.ActivityThread.access$800(ActivityThread.java:139)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1210)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:136)
at android.app.ActivityThread.main(ActivityThread.java:5086)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:515)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:785)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:601)
at dalvik.system.NativeStart.main(Native Method)
Caused by: java.lang.NullPointerException
at com.facebook.login.LoginFragment.onCreate(LoginFragment.java:68)
at android.support.v4.app.Fragment.performCreate(Fragment.java:1763)
at android.support.v4.app.FragmentManagerImpl.moveToState(FragmentManager.java:915)
at android.support.v4.app.FragmentManagerImpl.moveToState(FragmentManager.java:1136)
at android.support.v4.app.BackStackRecord.run(BackStackRecord.java:739)
at android.support.v4.app.FragmentManagerImpl.execPendingActions(FragmentManager.java:1499)
at android.support.v4.app.FragmentActivity.onStart(FragmentActivity.java:548)
at android.app.Instrumentation.callActivityOnStart(Instrumentation.java:1194)
at android.app.Activity.performStart(Activity.java:5258)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2171)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2257)
at android.app.ActivityThread.access$800(ActivityThread.java:139)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1210)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:136)
at android.app.ActivityThread.main(ActivityThread.java:5086)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:515)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:785)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:601)
at dalvik.system.NativeStart.main(Native Method)
Corresponding manifest entry
<activity android:name="com.facebook.FacebookActivity"
android:configChanges=
"keyboard|keyboardHidden|screenLayout|screenSize|orientation"
android:theme="@android:style/Theme.Translucent.NoTitleBar"
android:label="@string/app_name" />
App id is set inside onCreate
FacebookSdk.setApplicationId(FacebookData.APP_ID);
FacebookSdk.sdkInitialize(getApplicationContext());
Immediately after logging in, I get a response that the login has been canceled. Then the application will crash.
Facebook code reporting the crash:
this.callingPackage = this.getActivity().getCallingActivity().getPackageName();
My permissions:
private static final String[] READ_PERMISSIONS = new String[]{"public_profile", "user_events", "user_birthday", "email"};
source to share
Found out what it broke. Login method crashes on facebook LoginFragment if calling activity is set to singleInstance. I don't know if there is a workaround.
Edit:
It looks like Facebook has partially fixed the issue in SDK 4.1
4.0:
this.callingPackage = this.getActivity().getCallingActivity().getPackageName();
This results in NPE when login is called from the singleInstance operation.
Now it looks like LoginActivity will exit and report an error if this happens.
// If the calling package is null, this generally means that the callee was started
// with a launchMode of singleInstance. Unfortunately, Android does not allow a result
// to be set when the callee is a singleInstance, so we log an error and return.
if (callingPackage == null) {
Log.e(TAG, NULL_CALLING_PKG_ERROR_MSG);
getActivity().finish();
return;
}
source to share
there have been changes in how to implement certain features in the Android Android SDK, first:
You are not setting the applicationId code , it can now be executed using the metadata tag in the AndroidManifest.xml file .
Here's an example:
Before the closing tag in the manifest, you must set:
<!-- Facebook Integration -->
<activity
android:name="com.facebook.FacebookActivity"
android:configChanges="keyboard|keyboardHidden|screenLayout|screenSize|orientation"
android:label="@string/app_name"
android:theme="@android:style/Theme.Translucent.NoTitleBar" />
<meta-data
android:name="com.facebook.sdk.ApplicationId"
android:value="@string/facebook_id" />
Now, in your onCreate, you use the new LoginManager class for all your login calls that don't require a UI, as an example in the documentation below:
@Override
public void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
FacebookSdk.sdkInitialize(this.getApplicationContext());
callbackManager = CallbackManager.Factory.create();
LoginManager.getInstance().registerCallback(callbackManager,
new FacebookCallback<LoginResult>() {
@Override
public void onSuccess(LoginResult loginResult) {
// App code
}
@Override
public void onCancel() {
// App code
}
@Override
public void onError(FacebookException exception) {
// App code
}
});
}
You can always see all changes and documents for the new SDK here
UPDATE:
Below is an example of how to pass permissions using Array.AsList();
... logInWithReadPermissions(this, Arrays.asList("public_profile", "email");
source to share