Android FragmentManager BackStackRecord.run throwing NullPointerException

最新推荐文章于 2019-11-26 17:56:23 发布

转载最新推荐文章于 2019-11-26 17:56:23 发布 · 3.4k 阅读

Android 专栏收录该内容

471 篇文章

订阅专栏

本文解决了在Android应用中操作Fragments时出现的空指针异常问题，详细介绍了错误发生的原因及如何避免此问题的发生。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

在做hide () show 等操作的时候判空一下就解决这个问题了.

EDIT2: Answered my own question below

I sometimes get the following exception when working with Fragments:

11-15 09:04:21.023: E/AndroidRuntime(4057): FATAL EXCEPTION: main
11-15 09:04:21.023: E/AndroidRuntime(4057): java.lang.NullPointerException
11-15 09:04:21.023: E/AndroidRuntime(4057):     at android.support.v4.app.BackStackRecord.run(BackStackRecord.java:591)
11-15 09:04:21.023: E/AndroidRuntime(4057):     at android.support.v4.app.FragmentManagerImpl.execPendingActions(FragmentManager.java:1416)
11-15 09:04:21.023: E/AndroidRuntime(4057):     at android.support.v4.app.FragmentManagerImpl$1.run(FragmentManager.java:420)
11-15 09:04:21.023: E/AndroidRuntime(4057):     at android.os.Handler.handleCallback(Handler.java:615)
11-15 09:04:21.023: E/AndroidRuntime(4057):     at android.os.Handler.dispatchMessage(Handler.java:92)
11-15 09:04:21.023: E/AndroidRuntime(4057):     at android.os.Looper.loop(Looper.java:137)
11-15 09:04:21.023: E/AndroidRuntime(4057):     at android.app.ActivityThread.main(ActivityThread.java:4745)
11-15 09:04:21.023: E/AndroidRuntime(4057):     at java.lang.reflect.Method.invokeNative(Native Method)
11-15 09:04:21.023: E/AndroidRuntime(4057):     at java.lang.reflect.Method.invoke(Method.java:511)
11-15 09:04:21.023: E/AndroidRuntime(4057):     at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:786)
11-15 09:04:21.023: E/AndroidRuntime(4057):     at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:553)
11-15 09:04:21.023: E/AndroidRuntime(4057):     at dalvik.system.NativeStart.main(Native Method)

I can't seem to figure out what exactly is causing this? I think it has to do with the backstack of fragments not being cleaned up right when removing fragments.

EDIT1: The exception occurs when run() of BackStackRecord is called thru execPendingTransactions(). When it tries to remove a fragment from the manager.

case OP_REMOVE: {
  Fragment f = op.fragment;
  f.mNextAnim = op.exitAnim; <----
  mManager.removeFragment(f, mTransition, mTransitionStyle);
}
break;

Answering my own question:
This exception is (eventually) thrown when you call FragmentTransaction.remove(null); and FragmentTransaction.commit();
EDIT: And also, like Twice Circled and shinyuX point out in the comment; when calling the .show(null) or .add(null), attach(null) and .detach(null) methods, and probably also .hide(null)
After calling commit(), the transaction will be queued in the FragmentManager. As a result, when the operation is being processed after you explicitly call FragmentManager.executePendingTransactions(), or when the FragmentManager queue thread calls it, it throws a NullPointerException.
In my case, I was maintaining fragment states in a global object. There I checked if the fragment was showing or not, and then removed visible fragments. But because I started a new FragmentActivity, these states were still set to true while they were not visible. So this is a design error.
Other then fixing the design error, the solution was simple: check if FragmentManager.findFragmentByTag() returned null before removing the fragment.