Map region lost on navigation (Android only)

[VadymVashchuk]

Summary

I am using @react-navigation/native-stack, react-native 0.79 (new Architecture) and noticed an issue with new versions of this package.
When I navigate from screen with map to another screen and go back, map loses it's position. And it is not even rerendered. Only android.

Reproducible sample code

const MainScreen = () => {
  return (
    <View style={{flex: 1}}>
      <MapView style={{flex: 1}} provider={'google'} />
      <Pressable onPress={() => navigationRef.navigate('Profile'} style={{position: 'absolute', top: 50, left: 50, backgroundColor: 'red', width: 50, height: 50}}></Pressable>
    </View>
  );
};

export default MainScreen;

Steps to reproduce

1. MainScreen has . It is as simple as it could be.
2. We navigate to another screen with navigation.navigate('screenB') - common pattern.
3. We go back go MainScreen (no matter how, swiper or navigation.goBack())
4. Map loses it's position and shows default position if Africa with max zoom level I suppose.

Expected result

Like in IOS map should not change it's region.

Actual result

Map changes position although it's component is not rerendered.

React Native Maps Version

1.24.3, maybe earlier

What platforms are you seeing the problem on?

Android

React Native Version

0.79.1 (new Architecture)

What version of Expo are you using?

Not using Expo

Device(s)

Samsung A05

Additional information

No response

[markwilcox]

We also have this issue. Additionally, trying to animateToRegion via the ref fails after navigating away and back because the ref no longer points to the native view. Seems like the teardown and restore of the native view doesn't work properly in the new architecture on Android.

I'd love to try to help fix it, but I'm not sure I understand how it's supposed to work with the new architecture.

[noe4400]

What worked for me was downgrading to version 1.24.2.

[CongCaoSOF]

I also had the app closed for no reason.

[markwilcox]

What worked for me was downgrading to version 1.24.2.

Downgrading to 1.24.2 does indeed resolve this, but the change from 1.24.2 to 1.24.3 is a fix for an Android crash bug, so you might not want that if you get the crash.

[kstolk]

Same issue here on android only. Navigating to a location does not work anymore since this version.

[LukasB-DEV]

have the same issue @salah-ghanim can you take a look into this?

[Bilalget]

have the same issue @salah-ghanim can you take a look into this?

[rubiagul280]

same issue on Expo. Even after explicitly setting the region again, it's not working. We have access to the current location and coordinates, but the map is not updating accordingly.

If anyone has found a solution, please let me know.

[flmalte]

I'm experiencing the same issue, which is the final obstacle preventing me from upgrading to the new architecture.

[nahuelprinsich]

Same issue here using RN 0.79.2 and RNM 1.24.3.
I lose the location and markers when return from another screen.

[spsaucier]

I've worked around this issue for now by making the maps re-render on screen focus -- incrementing the key (on Android only) each time it's focused.

[lorenzomilesi]

@salah-ghanim I think the problem here is that, from this commit, the function detachLifecycleObserver is being called when the screen looses the focus (->onDetachedFromWindow).