onSaveInstanceState已调用但onCreate中savedInstanceState为空求助

Hey there, let's break down why you're hitting that NullPointerException when trying to restore your saved state, even though onSaveInstanceState is executing properly. Here are the key fixes and checks you need to make:

1. 先判断savedInstanceState是否为空（最直接的NPE原因） #

Your current code calls savedInstanceState.getSerializable() without first checking if savedInstanceState is null. Remember: savedInstanceState is only non-null when the Activity is being recreated after being destroyed by the system (like during a screen rotation or when the app is killed due to low memory). On a fresh launch, it's always null.

Fix your onCreate method to add a null check first:

@Override
protected void onCreate(Bundle savedInstanceState) {
    super.onCreate(savedInstanceState);
    setContentView(R.layout.mb_activity);
    // Initialize default empty lists first
    mBList = new ArrayList<MBClass>();
    mKList = new ArrayList<MKClass>();
    nAList = new ArrayList<AClass>();
    aList = new ArrayList<AClass>();
    
    // Only restore state if savedInstanceState exists
    if (savedInstanceState != null) {
        try {
            mBList = (ArrayList<MBClass>) savedInstanceState.getSerializable("MBList");
            mKList = (ArrayList<MKClass>) savedInstanceState.getSerializable("MKList");
            aList = (ArrayList<AClass>) savedInstanceState.getSerializable("AList");
            nAList = (ArrayList<AClass>) savedInstanceState.getSerializable("NAList");
            Log.i("MB", "State restored successfully");
        } catch (ClassCastException e) {
            // Catch class cast issues instead of NPE here
            Log.e("MB", "Failed to cast saved state objects", e);
        }
    } else {
        Log.i("MB", "No saved state available (fresh launch)");
    }
}

2. 调整onSaveInstanceState中super调用的顺序 #

You're currently adding your data to the bundle before calling super.onSaveInstanceState(savedInstanceState). It's better to call the super method first to let the system save the default Activity state, then add your custom data:

@Override
public void onSaveInstanceState(Bundle savedInstanceState) {
    super.onSaveInstanceState(savedInstanceState); // Call super first
    // Now add your custom serializable data
    savedInstanceState.putSerializable("MKList", (Serializable) mKList);
    savedInstanceState.putSerializable("MBList", (Serializable) mBList);
    savedInstanceState.putSerializable("NAList", (Serializable) nAList);
    savedInstanceState.putSerializable("AList", (Serializable) aList);
    Log.i("MB", "onSaveInstanceState executed");
}

3. 检查Activity的Manifest配置 #

Make sure your Activity isn't configured to skip state saving:

• Remove android:noHistory="true" if it's set (this tells the system not to keep the Activity in history, so state isn't saved)
• If you've set android:configChanges (like orientation|screenSize), note that this prevents the Activity from being recreated during those config changes—so onCreate won't be called again, and savedInstanceState will stay null for those scenarios.

4. Verify your Serializable classes are fully compatible #

Even though you said your classes implement Serializable, double-check:

• All member variables in MBClass, MKClass, and AClass are either serializable (implement Serializable) or marked with the transient keyword (to exclude them from serialization)
• None of the classes have non-serializable dependencies like Context, View, or other Android framework objects (these will break serialization silently in some cases)

5. Test the right scenario #

To properly test state restoration:

• Enable "Don't keep activities" in Developer Options, then switch your app to the background and back to the foreground
• Rotate the screen (make sure auto-rotate is enabled and you haven't locked the orientation)

These actions will force the system to destroy and recreate your Activity, which is when savedInstanceState should be populated.

内容的提问来源于stack exchange，提问作者Maximilian Notar