Android中ViewPager第三个Fragment无法存储HashMap问题

Alright, let's tackle this issue—you've got three Fragments in a ViewPager, the first two can successfully retrieve the Image object with its HashMap from the Bundle, but the third one's HashMap is missing. Here are the most likely causes and fixes to get this sorted:

1. Double-Check Your Image Parcelable Implementation #

The #1 culprit here is almost always an incorrect Parcelable setup for the HashMap in your Image class. Parcelable is strict about the order of writing/reading data, and if you mess that up, data gets lost or corrupted—especially in Fragments that might be delayed in initialization (like the third one in your ViewPager).

Make sure your Image class handles the HashMap correctly:

• In writeToParcel, write the HashMap before any other fields (or at least in an order that matches how you read it):

  @Override
  public void writeToParcel(Parcel dest, int flags) {
      dest.writeMap(imageHashMap); // Write HashMap first
      // Then write your other fields (like image paths, IDs, etc.)
  }
  

• In the Parcel constructor (used by the CREATOR), read the HashMap in the exact same order you wrote it:

  protected Image(Parcel in) {
      imageHashMap = in.readHashMap(HashMap.class.getClassLoader()); // Read HashMap first
      // Then read your other fields
  }
  

• Also confirm that the keys and values in your HashMap are Parcelable-compatible (e.g., String, Integer, or custom classes that also implement Parcelable). Non-parcelable types will silently fail here.

2. Account for ViewPager's Offscreen Preloading & Fragment Reconstruction #

ViewPager has a default offscreenPageLimit of 1, which means it only keeps the current Fragment and one adjacent one in memory. The third Fragment might get destroyed and recreated when you swipe to it, and if your Parcelable isn't handling state correctly during reconstruction, the HashMap could go missing.

Try forcing ViewPager to keep all three Fragments in memory temporarily to test this:

viewPager.setOffscreenPageLimit(2);

If the third Fragment works after this, it confirms the issue was related to Fragment reconstruction. You can keep this setting if your Fragments are lightweight, or fix the Parcelable implementation to handle reconstruction properly.

3. Verify the Image Object Passed to the Third Fragment #

It sounds obvious, but double-check that the Image object you're passing to the third Fragment actually has a non-empty HashMap before you put it into the Bundle. Add a log statement in your newInstance method to confirm:

public static InfoFragment newInstance(Image image, String path) {
    Bundle args = new Bundle();
    // Log to check HashMap state
    Log.d("ImageDebug", "Third Fragment HashMap size: " + image.getImageHashMap().size());
    args.putParcelable("object", image);
    args.putString("path", path);
    InfoFragment fragment = new InfoFragment();
    fragment.setArguments(args);
    return fragment;
}

If the log shows an empty HashMap here, the problem isn't with the Fragment or Bundle—it's with the Image object you're passing in the first place.

4. Fallback: Use JSON Serialization Instead of Parcelable #

If Parcelable continues to give you grief with HashMaps, a reliable workaround is to serialize your Image object to a JSON string and pass that instead. This avoids all the quirks of Parcelable with complex collections:

• In your newInstance method:

  public static InfoFragment newInstance(Image image, String path) {
      Bundle args = new Bundle();
      // Convert Image to JSON string
      String imageJson = new Gson().toJson(image);
      args.putString("image_json", imageJson);
      args.putString("path", path);
      InfoFragment fragment = new InfoFragment();
      fragment.setArguments(args);
      return fragment;
  }
  

• In your Fragment's onCreate method:

  @Override
  public void onCreate(Bundle savedInstanceState) {
      super.onCreate(savedInstanceState);
      String imageJson = getArguments().getString("image_json");
      Image image = new Gson().fromJson(imageJson, Image.class);
      // Now use your image object—HashMap should be intact
  }
  

(Note: You'll need to add the Gson dependency to your build.gradle if you don't have it already.)

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