Android Java中Google Map二次加载时出现错误问题

Hey there! I’ve run into this exact Google Map reload issue with Fragments before—usually happens when navigating back to the Fragment or recreating it. Let’s break down what’s going wrong and how to fix it.

Common Root Causes #

The problem typically stems from one of these two issues:

• Using the framework’s MapFragment inside a nested android.app.Fragment causes lifecycle conflicts when the Fragment reloads.
• Failing to properly manage the GoogleMap instance leads to duplicate initialization attempts on second load.

Step-by-Step Fix #

1. Switch to SupportMapFragment #

First, replace the framework MapFragment with the support library version. It plays far nicer with Fragment lifecycle events, especially during reloads.

Update your imports:

// Replace this
import com.google.android.gms.maps.MapFragment;
// With this
import com.google.android.gms.maps.SupportMapFragment;

Pro tip: If you’re not already using support Fragments, update your base Fragment import to android.support.v4.app.Fragment too for better compatibility.

2. Properly Initialize & Manage the Map Instance #

Instead of grabbing the map immediately, use getMapAsync() to wait for it to be ready. Also, use getChildFragmentManager() to access the nested map fragment correctly.

Here’s the corrected code for your MapPage.java:

package com.example.cheng.freequeue;

import android.os.AsyncTask;
import android.os.Bundle;
import android.support.annotation.Nullable;
import android.util.Log;
import android.view.LayoutInflater;
import android.view.View;
import android.view.ViewGroup;
import android.support.v4.app.Fragment;

import com.google.android.gms.maps.CameraUpdateFactory;
import com.google.android.gms.maps.GoogleMap;
import com.google.android.gms.maps.OnMapReadyCallback;
import com.google.android.gms.maps.SupportMapFragment;
import com.google.android.gms.maps.model.LatLng;

public class MapPage extends Fragment implements OnMapReadyCallback {

    private GoogleMap mMap; // Hold the map instance as a member variable

    @Nullable
    @Override
    public View onCreateView(LayoutInflater inflater, @Nullable ViewGroup container, @Nullable Bundle savedInstanceState) {
        View view = inflater.inflate(R.layout.your_map_layout, container, false);

        // Get the SupportMapFragment and request map ready callback
        SupportMapFragment mapFragment = (SupportMapFragment) getChildFragmentManager()
                .findFragmentById(R.id.map);
        if (mapFragment != null) {
            mapFragment.getMapAsync(this);
        }

        return view;
    }

    @Override
    public void onMapReady(GoogleMap googleMap) {
        mMap = googleMap;

        // Your map setup code here (e.g., move camera, add markers)
        LatLng defaultLocation = new LatLng(37.7749, -122.4194); // Example: San Francisco
        mMap.moveCamera(CameraUpdateFactory.newLatLngZoom(defaultLocation, 12));
    }

    @Override
    public void onDestroyView() {
        super.onDestroyView();
        // Clear the map instance to avoid memory leaks and duplicate initialization
        mMap = null;
        // Optional: Remove the map fragment to clean up resources
        SupportMapFragment mapFragment = (SupportMapFragment) getChildFragmentManager()
                .findFragmentById(R.id.map);
        if (mapFragment != null) {
            getChildFragmentManager().beginTransaction().remove(mapFragment).commit();
        }
    }
}

3. Update Your Layout File #

Make sure your layout uses the support map fragment instead of the framework one:

<fragment
    android:id="@+id/map"
    android:name="com.google.android.gms.maps.SupportMapFragment"
    android:layout_width="match_parent"
    android:layout_height="match_parent" />

Key Notes #

• Lifecycle Cleanup: Clearing the GoogleMap instance in onDestroyView prevents duplicate map instances from being created when the Fragment reloads.
• Child Fragment Manager: Using this instead of getFragmentManager() ensures we’re accessing the nested map fragment correctly, avoiding conflicts during Fragment recreation.

This should resolve the second-load error you’re facing. Let me know if you hit any other snags!

内容的提问来源于stack exchange，提问作者Toh Kok Cheng