Android Java中OsmDroid地图Fragment状态无法正确保存的问题

我正在使用Android Studio开发Java版Android应用，采用MVVM架构搭配Jetpack Compose，应用底部导航栏包含多个Fragment，其中首页Fragment使用OsmDroid实现地图功能。目前应用可正常运行，但将地图移动到指定位置后切换其他Fragment，返回时地图会重置到默认的当前定位位置。我尝试通过onSaveInstanceState和onCreateView方法保存恢复地图状态，但调试发现savedInstanceState始终为null，对应的恢复代码从未执行。

问题代码 #

package com.seaguard.ui.home;

import android.os.Bundle;
import android.view.LayoutInflater;
import android.view.View;
import android.view.ViewGroup;

import androidx.annotation.NonNull;
import androidx.fragment.app.Fragment;
import androidx.lifecycle.ViewModelProvider;

import com.seaguard.databinding.FragmentHomeBinding;

import org.osmdroid.api.IGeoPoint;
import org.osmdroid.tileprovider.tilesource.TileSourceFactory;
import org.osmdroid.util.GeoPoint;
import org.osmdroid.views.MapController;
import org.osmdroid.views.MapView;
import org.osmdroid.views.overlay.mylocation.GpsMyLocationProvider;
import org.osmdroid.views.overlay.mylocation.MyLocationNewOverlay;


public class HomeFragment extends Fragment {
    private FragmentHomeBinding binding;
    private MapView map;

    public View onCreateView(@NonNull LayoutInflater inflater, ViewGroup container, Bundle savedInstanceState) {
        if(savedInstanceState == null) {
            System.out.println("BBB");
            HomeViewModel homeViewModel = new ViewModelProvider(requireActivity()).get(HomeViewModel.class);

            binding = FragmentHomeBinding.inflate(inflater, container, false);
            View root = binding.getRoot();

            // Map
            map = binding.map;
            map.setTileSource(TileSourceFactory.MAPNIK);
            map.setBuiltInZoomControls(false);
            map.setMultiTouchControls(true);

            MapController mapController = (MapController) map.getController();
            mapController.setCenter(new GeoPoint(41.8902, 12.4922)); // Rome
            mapController.setZoom(16);

            homeViewModel.setCallBack(() -> {
                //provider.addLocationSource(LocationManager.NETWORK_PROVIDER);
                MyLocationNewOverlay location = new MyLocationNewOverlay(new GpsMyLocationProvider(map.getContext()), map);
                location.enableMyLocation();
                map.getOverlays().add(location);

                location.runOnFirstFix(() -> {
                    requireActivity().runOnUiThread(() -> map.getController().animateTo(location.getMyLocation()));
                });
                return location;
            });
            if (homeViewModel.permissionsRequested()) homeViewModel.setLocation();
            return root;
        }else{

            System.out.println("AAAA");

            View root = binding.getRoot();

            double latitude = savedInstanceState.getDouble("latitude", 41.8902);
            double longitude = savedInstanceState.getDouble("longitude", 12.4922);
            int zoom_level = savedInstanceState.getInt("zoom_level", 16);
            float map_orientation = savedInstanceState.getFloat("map_orientation", 0);

            GeoPoint restoredCenter = new GeoPoint(latitude, longitude);

            map.getController().setCenter(restoredCenter);
            map.getController().setZoom(zoom_level);
            map.setMapOrientation(map_orientation);

            return root;
        }
    }


    @Override
    public void onSaveInstanceState(@NonNull Bundle outState) {
        super.onSaveInstanceState(outState);

            IGeoPoint center = map.getMapCenter();
            outState.putDouble("latitude", center.getLatitudeE6() / 1e6);
            outState.putDouble("longitude", center.getLongitudeE6() / 1e6);

            outState.putInt("zoom_level", map.getZoomLevel());

            outState.putFloat("map_orientation", map.getMapOrientation());

    }

}

问题原因分析 #

• Fragment生命周期特性：底部导航切换Fragment时，默认配置下Fragment会被完全销毁并重建，savedInstanceState仅在Fragment因系统回收（如内存不足）时才会被保留，主动切换场景下不会触发状态保存。
• onCreateView逻辑错误：savedInstanceState != null分支中未初始化binding，直接调用binding.getRoot()会触发空指针，且地图初始化逻辑完全缺失，即使状态有值也无法恢复。
• 未利用OsmDroid原生状态管理：OsmDroid的MapView自带状态保存方法，但当前代码未调用，浪费了原生能力。

解决方案 #

方案1：基于ViewModel保存状态（推荐，适配MVVM架构） #

利用ViewModel的生命周期特性，将地图状态存储在ViewModel中，不受Fragment销毁重建影响：

1. 修改HomeViewModel添加状态变量：

public class HomeViewModel extends ViewModel {
    private MutableLiveData<GeoPoint> mapCenter = new MutableLiveData<>(new GeoPoint(41.8902, 12.4922));
    private MutableLiveData<Integer> mapZoom = new MutableLiveData<>(16);
    private MutableLiveData<Float> mapOrientation = new MutableLiveData<>(0f);

    public LiveData<GeoPoint> getMapCenter() { return mapCenter; }
    public void setMapCenter(GeoPoint center) { mapCenter.setValue(center); }

    public LiveData<Integer> getMapZoom() { return mapZoom; }
    public void setMapZoom(int zoom) { mapZoom.setValue(zoom); }

    public LiveData<Float> getMapOrientation() { return mapOrientation; }
    public void setMapOrientation(float orientation) { mapOrientation.setValue(orientation); }

    // 原有业务代码...
}

2. 修改HomeFragment逻辑：

public class HomeFragment extends Fragment {
    private FragmentHomeBinding binding;
    private MapView map;
    private HomeViewModel homeViewModel;

    @Override
    public View onCreateView(@NonNull LayoutInflater inflater, ViewGroup container, Bundle savedInstanceState) {
        homeViewModel = new ViewModelProvider(requireActivity()).get(HomeViewModel.class);
        binding = FragmentHomeBinding.inflate(inflater, container, false);
        View root = binding.getRoot();

        // 初始化地图基础配置
        map = binding.map;
        map.setTileSource(TileSourceFactory.MAPNIK);
        map.setBuiltInZoomControls(false);
        map.setMultiTouchControls(true);

        // 恢复ViewModel中存储的地图状态
        GeoPoint center = homeViewModel.getMapCenter().getValue();
        Integer zoom = homeViewModel.getMapZoom().getValue();
        Float orientation = homeViewModel.getMapOrientation().getValue();
        if (center != null) map.getController().setCenter(center);
        if (zoom != null) map.getController().setZoom(zoom);
        if (orientation != null) map.setMapOrientation(orientation);

        // 监听地图状态变化，实时保存到ViewModel
        map.addOnLayoutChangeListener((v, left, top, right, bottom, oldLeft, oldTop, oldRight, oldBottom) -> {
            homeViewModel.setMapCenter((GeoPoint) map.getMapCenter());
            homeViewModel.setMapZoom(map.getZoomLevel());
            homeViewModel.setMapOrientation(map.getMapOrientation());
        });

        // 定位逻辑优化：仅首次定位且未手动调整地图时跳转
        homeViewModel.setCallBack(() -> {
            MyLocationNewOverlay location = new MyLocationNewOverlay(new GpsMyLocationProvider(map.getContext()), map);
            location.enableMyLocation();
            map.getOverlays().add(location);

            if (homeViewModel.getMapCenter().getValue().equals(new GeoPoint(41.8902, 12.4922))) {
                location.runOnFirstFix(() -> {
                    requireActivity().runOnUiThread(() -> {
                        GeoPoint myLoc = location.getMyLocation();
                        if (myLoc != null) {
                            map.getController().animateTo(myLoc);
                            homeViewModel.setMapCenter(myLoc);
                        }
                    });
                });
            }
            return location;
        });
        if (homeViewModel.permissionsRequested()) homeViewModel.setLocation();

        return root;
    }

    // 无需再用onSaveInstanceState，状态已由ViewModel维护
}

方案2：保留Fragment实例（临时方案，不推荐） #

在Fragment初始化时设置保留实例，避免切换时被销毁：

@Override
public void onCreate(Bundle savedInstanceState) {
    super.onCreate(savedInstanceState);
    setRetainInstance(true);
}

该方式会长期保留Fragment实例，可能引发内存泄漏，不符合MVVM架构设计，仅作为临时应急方案。

方案3：利用OsmDroid原生状态保存 #

让MapView自行处理状态保存与恢复，同时确保Fragment状态能被正确传递：

@Override
public void onSaveInstanceState(@NonNull Bundle outState) {
    super.onSaveInstanceState(outState);
    map.onSaveInstanceState(outState); // 让MapView保存自身状态
}

@Override
public void onViewStateRestored(@Nullable Bundle savedInstanceState) {
    super.onViewStateRestored(savedInstanceState);
    if (savedInstanceState != null) {
        map.onRestoreInstanceState(savedInstanceState); // 恢复MapView状态
    }
}

此方式依赖Fragment状态是否被系统保留，底部导航切换场景下依然可能失效，不如ViewModel方案可靠。

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