fix: pin ViewTreeLifecycleOwner/SavedStateRegistryOwner on MapView to prevent info window crash

[kikoso]

Summary

Fixes #971.

On compose-ui 1.11+, MarkerInfoWindow / MarkerInfoWindowContent can crash with:

java.lang.IllegalStateException: Composed into the View which doesn't propagate ViewTreeLifecycleOwner!

The Maps SDK measures the info-window ComposeView from its own Handler, asynchronously. If that measure lands after Compose has unparented the MapView (e.g. LazyColumn recycling/detach), the ComposeView can no longer resolve a ViewTreeLifecycleOwner/ViewTreeSavedStateRegistryOwner by walking up its ancestors, because those tags live on the AndroidView holder — the MapView's parent — not on the MapView itself. AbstractComposeView.onMeasure then throws (this became fatal in compose-ui 1.11, which moved owner resolution into onMeasure; on 1.10 it silently rendered blank instead).

Fix

Two commits:

1. Pin the ViewTree owners onto the MapView (GoogleMap.kt) — at creation in the AndroidView factory, and on every update in case the owner identity changes. This keeps the owner lookup resolvable from within the map's own subtree regardless of where Compose has parented the MapView, without changing behavior while attached (same owner instances AndroidView already assigns to the parent).

2. Handle the now-reachable zero-size render gracefully (MapComposeViewRender.kt, ComposeInfoWindowAdapter.kt) — with (1) alone, the original crash is gone, but on this codebase's bitmap-based info-window rendering (fix: avoid re-parenting crash for MarkerInfoWindowContent/MarkerInfoWindowComposable #953) the same detached-render race surfaces a second crash: renderComposableToBitmap's own check() rejects the zero-size measurement that naturally results from compositing a ComposeView that never got a real window attachment. A MapView mid-teardown has nothing worth rendering anyway, so that specific case (zero-size and not attached to window) now returns null instead of throwing, propagated through the already-nullable getInfoContents()/getInfoWindow(). Zero-size content on an attached MapView still throws with the original message — that's a genuine content-authoring bug, not a teardown race.

Test plan

• ./gradlew :maps-compose:compileDebugKotlin — builds clean
• ./gradlew :maps-compose:lintDebug — no new issues
• Verified on a physical device (Pixel 4, Android 13, GMS 26.32.62, phoenix renderer) using the exact LazyColumn-recycling repro from Maps Compose: MarkerInfoWindow crashes with "Composed into the View which doesn't propagate ViewTreeLifecycleOwner!" on compose-ui 1.11+ when the map is detached #971 (showInfoWindow() + scroll-out in the same beat, repeated in a loop):
  • Baseline (no fix): crashes with the exact reported ViewTreeLifecycleOwner IllegalStateException, stack trace matching Maps Compose: MarkerInfoWindow crashes with "Composed into the View which doesn't propagate ViewTreeLifecycleOwner!" on compose-ui 1.11+ when the map is detached #971 line-for-line, within the first ~20 cycles.
  • Fix 1 only: original crash gone, but a different crash appears (renderComposableToBitmap's zero-size check()) — this codebase's info-window rendering had already been rewritten to a bitmap-based approach (fix: avoid re-parenting crash for MarkerInfoWindowContent/MarkerInfoWindowComposable #953) since 8.4.0, exposing this second issue.
  • Both fixes applied: 420+ cycles over 60s, no crash, process alive throughout.

🤖 Generated with Claude Code

[googlemaps-bot]

Code Coverage

Overall Project	25.74%	❌

There is no coverage information present for the Files changed

[LoyalAbbas]

LGTM