currentCameraPositionState does not handle new CameraPositionState object
bubenheimer opened this issue · comments
android-maps-compose 4.3.0
The currentCameraPositionState property references only the CameraPositionState object that was initially provided to GoogleMap(). If the caller provides a new CameraPositionState object it is ignored by the currentCameraPositionState property. While providing a new CameraPositionState object is not recommended, it should not break the code.
The culprit is here, the CompositionLocalProvider() uses the originally provided cameraPositionState object rather than the delegated version from rememberUpdatedState():
🎉 This issue has been resolved in version 4.3.2 🎉
The release is available on:
v4.3.2- GitHub release
Your semantic-release bot 📦🚀