Crash when opening the map #584
Comments
JeevanRupacha
added
triage me
|
Hi @JeevanRupacha , The error strack trace does not seem to be related to the code snippet. Are you doing something else besides trying to cluster, like executing a network call? |
|
@kikoso I am doing clustering based on already fetched data. I mean even I didn't do any clustering and just run the only above code I got crash. By the way this crash happens when I try to open google map quickly after app launch and if I wait minute or more and execute then works very fine. Just This code: |
|
I have the same issue with maps compose 6.1.1, compose 1.6.10, kotlin 2.0.0. App just hangs for a second and then crashes with the same stacktrace private val StaticMapUi = MapUiSettings(
zoomControlsEnabled = false,
zoomGesturesEnabled = false,
compassEnabled = false,
indoorLevelPickerEnabled = false,
mapToolbarEnabled = false,
myLocationButtonEnabled = false,
rotationGesturesEnabled = false,
scrollGesturesEnabled = false,
scrollGesturesEnabledDuringRotateOrZoom = false,
tiltGesturesEnabled = false
)
...
@Composable
fun Test() {
Column {
....
val markerPosition = LatLng(20.0, 20.0)
val cameraPositionState = rememberCameraPositionState {
position = CameraPosition.fromLatLngZoom(markerPosition, MapZoom)
}
GoogleMap(
cameraPositionState = cameraPositionState,
modifier = Modifier.Companion
.fillMaxWidth()
.height(RestaurantMapHeight)
.clip(MaterialTheme.shapes.large),
uiSettings = StaticMapUi,
) {
Marker(
state = MarkerState(position = markerPosition),
)
}
....
}
} |
|
same here. |
|
We experience the same issue: https://byairapp-sl.sentry.io/share/issue/7a338366b2a24cc5b451e9bb5e5260d1/ upd: |
|
I have the same problem. If you do not open the map for more than 15 minutes after running the app, the above conflict will occur. There are currently two collisions: m.fdy.c and m.feb.c. Below is my stack.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Environment details
Code example
Stack trace
Thanks!
The text was updated successfully, but these errors were encountered: