旋转模拟器时按钮文本不显示，保存Fragment状态遇空指针问题

Hey there, let's break down your problem step by step and fix those issues one by one!

First: Fix the Button Null Pointer Exception #

The root cause here is that you're probably trying to access Button objects directly in state save/restore methods (like onSaveInstanceState), but those views haven't been recreated yet when the Fragment rebuilds after rotation. Instead of saving the Button objects themselves, save their text content (raw strings) and restore them after the views are initialized.

Here's how to adjust your Fragment code:

Save state properly:

@Override
public void onSaveInstanceState(@NonNull Bundle outState) {
    super.onSaveInstanceState(outState);
    // Save button texts (not the Button objects!)
    if (button1 != null) {
        outState.putString("BTN_1_TEXT", button1.getText().toString());
    }
    if (button2 != null) {
        outState.putString("BTN_2_TEXT", button2.getText().toString());
    }
    if (button3 != null) {
        outState.putString("BTN_3_TEXT", button3.getText().toString());
    }
    // Save TextView content too if needed
    if (textView1 != null) {
        outState.putString("TV_1_TEXT", textView1.getText().toString());
    }
    // Optional: Save RecyclerView layout state to keep scroll position
    if (recyclerView != null && recyclerView.getLayoutManager() != null) {
        outState.putParcelable("RV_LAYOUT", recyclerView.getLayoutManager().onSaveInstanceState());
    }
}

Restore state after view initialization:

@Nullable
@Override
public View onCreateView(@NonNull LayoutInflater inflater, @Nullable ViewGroup container, @Nullable Bundle savedInstanceState) {
    View view = inflater.inflate(R.layout.your_fragment_layout, container, false);
    
    // First, initialize all your views
    button1 = view.findViewById(R.id.button1);
    button2 = view.findViewById(R.id.button2);
    button3 = view.findViewById(R.id.button3);
    textView1 = view.findViewById(R.id.textView1);
    textView2 = view.findViewById(R.id.textView2);
    recyclerView = view.findViewById(R.id.recyclerView);
    
    // Now restore state if savedInstanceState exists
    if (savedInstanceState != null) {
        // Restore button texts
        String btn1Text = savedInstanceState.getString("BTN_1_TEXT");
        if (btn1Text != null) button1.setText(btn1Text);
        
        String btn2Text = savedInstanceState.getString("BTN_2_TEXT");
        if (btn2Text != null) button2.setText(btn2Text);
        
        String btn3Text = savedInstanceState.getString("BTN_3_TEXT");
        if (btn3Text != null) button3.setText(btn3Text);
        
        // Restore TextView content
        String tv1Text = savedInstanceState.getString("TV_1_TEXT");
        if (tv1Text != null) textView1.setText(tv1Text);
        
        // Restore RecyclerView scroll position
        Parcelable rvLayoutState = savedInstanceState.getParcelable("RV_LAYOUT");
        if (rvLayoutState != null) {
            recyclerView.getLayoutManager().onRestoreInstanceState(rvLayoutState);
        }
    }
    
    // Set up your RecyclerView adapter here
    setupRecyclerView();
    
    return view;
}

Second: Fix Language Switch & Missing Button Text Issues #

When you save the Fragment state, you're overriding the system's default behavior of reloading language-specific resources after rotation. Here's how to balance state preservation and language handling:

1. If you want rotation to keep the current language:

   • Add code to your Activity to persist the current Locale across recreation. For example, in attachBaseContext:

     @Override
     protected void attachBaseContext(Context newBase) {
         // Load your saved Locale (e.g., from SharedPreferences)
         Locale savedLocale = getSavedLocale(); // Implement this method to fetch stored locale
         Context updatedContext = LocaleHelper.setLocale(newBase, savedLocale);
         super.attachBaseContext(updatedContext);
     }
     

   • Only save button/text content if the user modified it (not the default language strings). For default text, let the system load the correct language resource automatically.

2. If you want rotation to switch language normally:

   • Don't save the default button/text state. Only save user-edited content (if any). This way, when the Fragment rebuilds, it loads the new language's resources automatically.

Also double-check your layout file: make sure Button android:text uses string resources (e.g., @string/button_submit) instead of hardcoded text. This ensures language switching works as expected.

Quick Tips to Avoid Future Issues #

• Never save view objects to Bundle—they can't be properly serialized. Always save raw data (strings, integers, etc.).
• Handle state restoration in onCreateView or onViewCreated (after views are initialized), not earlier lifecycle methods like onCreate.
• For RecyclerView, rely on your data source (e.g., ViewModel, Repository) to reload data after rotation instead of saving adapter data directly—it's more reliable.

内容的提问来源于stack exchange，提问作者Noura Ali