A modern programming language that makes developers happier.

kotlinlang

I have a problem with window insets (being always 0). Nothing works, neither `WindowInsets.navigationBars.getBottom(LocalDensity.current)` nor the `navigationBarsPadding()` -modifier.

This occurs when I have composable inside a `ComposeView` which itself is inside an `AndroidView` . Maybe this double injection screws up the insets? This is used as a way to show a `Fragment` inside an `Activity` which only uses `ComponentActivity.setContent()` to get into compose and everything else is handled inside compose only (e.g. navigating to different screens and some of those are simple composables but some are legacy fragments)

If you do put the same window insets code right before you do this loop of going from `compose -&gt; fragment -&gt; compose`
so by doing
`compose -&gt; Get insets here -&gt; fragment -&gt; compose`
Do you get the right insets? If I were you I’d try to do a minimal repro of this, to see that it’s not me breaking this somehow, or if it’s that this doesn’t work at all anyway.

Sorry for pinging you <@U011HA9T9SA> but if there’s someone who might know if this should work normally I think it would be you, so would be great if you could help out here :blush:

Most likely composition locals are not propagated through ComposeView here
Consider calling setParentCompositionContext on init with context of outer composition

You may also need to set `ComposeView.consumeWindowInsets` to `false` for your outermost `ComposeView`, to allow inset information to propagate to contained views:
<https://developer.android.com/reference/kotlin/androidx/compose/ui/platform/ComposeView#(androidx.compose.ui.platform.ComposeView).consumeWindowInsets()|https://developer.android.com/reference/kotlin/androidx/compose/ui/platform/ComposeView#(androidx.compose.ui.platfor[…]seView).consumeWindowInsets()>

There’s also a known limitation for consumption on the Compose side given by <https://issuetracker.google.com/issues/243778587>.

I’m not sure if `setParentCompositionContext` covers modifier locals that insets use?

Thank you for your great responses (learned a lot). I have solved my problem by simply checking if the fragment is using compose (only) or actually using the legacy view system and not adding an `AndroidView` if it doesn't :slightly_smiling_face:

Please, android specific compise issues should be posted on <#C04TPPEQKEJ|compose-android> not <#CJLTWPH7S|compose>