如何解决屏幕旋转时SearchView状态丢失及报错问题？

Hey there! Let's figure out why your SearchView is acting up when switching between portrait and landscape modes—this is a super common issue tied to how Android handles Activity lifecycle during orientation changes.

Common Causes & Fixes #

1. Activity Reconstruction Causes State Loss #

By default, Android destroys and recreates your Activity when the screen rotates. If you don't save the SearchView's current query or the filtered list state, you might end up with null references or inconsistent data that triggers errors.

Fix: Save and restore the search query
Add code to preserve the search text in onSaveInstanceState, then restore it when the Activity rebuilds:

@Override
protected void onSaveInstanceState(Bundle outState) {
    super.onSaveInstanceState(outState);
    // Save the current search query
    outState.putString("SAVED_SEARCH_QUERY", searchView.getQuery().toString());
}

@Override
protected void onCreate(Bundle savedInstanceState) {
    super.onCreate(savedInstanceState);
    setContentView(R.layout.your_activity_layout);
    
    // Initialize your SearchView, adapter, and data source here
    
    if (savedInstanceState != null) {
        String savedQuery = savedInstanceState.getString("SAVED_SEARCH_QUERY");
        if (!TextUtils.isEmpty(savedQuery)) {
            // Restore the query and trigger the filter
            searchView.setQuery(savedQuery, true);
        }
    }
}

2. Filtered Data Source Isn't Restored #

If you're using a filtered list with your adapter, the original or filtered data might not be properly reinitialized after the Activity rebuilds. This can lead to null pointers when the SearchView tries to apply filters.

Fix: Ensure data persistence

• Keep your original data source (like an ArrayList) as a global class variable, so it survives the Activity reconstruction.
• If your data is large or needs to persist beyond the Activity, load it from a local database or shared preferences instead of recreating it from scratch each time.
• When restoring the search query, re-run the filter logic on the restored data source.

3. Unhandled SearchView Callback Binding #

If you set up an OnQueryTextListener in onCreate but don't clean it up when the Activity is destroyed, you might end up with stale callbacks pointing to destroyed objects when the Activity rebuilds.

Fix: Manage callback lifecycle
Store the listener as a member variable and unbind it when the Activity is destroyed:

private SearchView.OnQueryTextListener searchQueryListener = new SearchView.OnQueryTextListener() {
    @Override
    public boolean onQueryTextSubmit(String query) {
        // Handle search submission
        return true;
    }

    @Override
    public boolean onQueryTextChange(String newText) {
        // Apply filter to your adapter
        yourAdapter.getFilter().filter(newText);
        return true;
    }
};

@Override
protected void onCreate(Bundle savedInstanceState) {
    super.onCreate(savedInstanceState);
    // ... initialization code
    searchView.setOnQueryTextListener(searchQueryListener);
}

@Override
protected void onDestroy() {
    super.onDestroy();
    if (searchView != null) {
        searchView.setOnQueryTextListener(null);
    }
}

4. Use the Error Stack Trace to Narrow Down #

If you haven't already, take a close look at the error log. Common issues here include:

• NullPointerException: Likely a null adapter, data source, or SearchView reference after reconstruction.
• IllegalStateException: Maybe trying to modify the adapter before it's attached to the RecyclerView/ListView.

The stack trace will point you directly to the line of code causing the problem—this is the fastest way to pinpoint the exact issue.

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