Skip to content

Maps Compose: Crash in GoogleMap.addMarker() with LatLngBounds latitude ordering exception #829

@lukemorris89

Description

@lukemorris89

Environment details

API / Library

  • Maps Compose – com.google.maps.android:maps-compose 6.12.2
  • Google Play services Maps 19.2.0

OS type and version

  • Android 10, 13, 15, 16

Devices

  • Google Pixel and Samsung Galaxy devices (various models)

Other environment information

  • Compose BOM: 2025.10.01
  • Crash observed since Jan 17 2026
  • Occurs during marker rendering via MarkerComposable
  • App uses LatLngBounds.Builder.include() exclusively and does not construct LatLngBounds(southwest, northeast) directly

Steps to reproduce

  • Currently not reproducible locally.
  • Crash is reported by a small but growing subset of production users.
  • Crash occurs while markers are being added to a Compose Google Map (MarkerComposable → GoogleMap.addMarker()).
  • No related app changes were deployed when the crash started appearing.

Notes:

  • Markers are added using Maps Compose (MarkerComposable)
  • Camera bounds are built using LatLngBounds.Builder.include()
  • The app does not manually construct LatLngBounds via its public constructor

Stack trace

Fatal Exception: java.lang.IllegalArgumentException:
southern latitude exceeds northern latitude (40.97989806962013 > -40.44694705960049)

at m140.cqy.c(:com.google.android.gms.policy_maps_core_dynamite@254515607@254515602025.843324832.843324832:10)
at com.google.android.gms.maps.model.LatLngBounds.<init>(com.google.android.gms:play-services-maps@@19.2.0:4)
at com.google.maps.api.android.lib6.lite.aa.c(:com.google.android.gms.policy_maps_core_dynamite@254515607@254515602025.843324832.843324832:53)
at com.google.maps.api.android.lib6.impl.cg.l(:com.google.android.gms.policy_maps_core_dynamite@254515607@254515602025.843324832.843324832:159)
at com.google.android.gms.maps.internal.j.bt(:com.google.android.gms.policy_maps_core_dynamite@254515607@254515602025.843324832.843324832:341)
at m140.ayi.onTransact(:com.google.android.gms.policy_maps_core_dynamite@254515607@254515602025.843324832.843324832:21)
at android.os.Binder.transact(Binder.java:1309)
at com.google.android.gms.internal.maps.zza.zzJ(zza.java:2)
at com.google.android.gms.maps.internal.zzg.addMarker(zzg.java:3)
at com.google.android.gms.maps.GoogleMap.addMarker(GoogleMap.java:3)
at com.google.maps.android.compose.MarkerKt.MarkerImpl_khPtz74$lambda$4$0(Marker.kt:1240)
at androidx.compose.runtime.changelist.Operation$InsertNodeFixup.execute(Operation.kt:731)
...

Additional context

  • The exception originates from LatLngBounds. while adding a marker.
  • The latitude values reported in the exception do not correspond to any coordinates passed to the map by the application.
  • The crash appears to occur inside Maps internal logic (Dynamite module) during marker insertion, possibly related to internal bounds or layout calculations.
  • The issue began appearing without relevant application changes, suggesting a potential regression in recent Maps / Dynamite releases.

Metadata

Metadata

Assignees

No one assigned

    Labels

    triage meI really want to be triaged.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions