Is anybody else trying out the nav3 library? I am ...

# compose-ios

[Kevin van Mierlo]

Is anybody else trying out the nav3 library? I am using 1.0.0-alpha06 of the nav3 and I also updated the compose multiplatform to 1.10.0-rc01, but am experiencing issues on the iOS side with the WindowInsets. I have a tabbar and in the screen where I use the tabbar I provide this modifier for the content within:

modifier = Modifier
                    .padding(it)
                    .consumeWindowInsets(it),

Inside if I check with onConsumedWindowInsetsChanged it correctly says these are the consumed insets:

consumed insets: (Insets(left=0, top=0, right=0, bottom=0) + PaddingValues(0.0.dp, 0.0.dp, 0.0.dp, 114.0.dp))

However, I have a FloatingActionButton which uses the following modifier:

modifier = Modifier
                    .align(Alignment.BottomEnd)
                    .safeDrawingPadding()
                    .padding(all = 16.dp),

But it has too much padding. I think it also gives back the navigation bar padding which should be consumed by the tabbar. Anybody else experienced this? On the Android side the WindowInsets are working as expected. And before the version updates it was also working as expected. But maybe something changed I have overlooked?

[Kevin van Mierlo]

Doesn't appear to be a nav3 problem. I've created an issue in case someone else has the same problem: https://youtrack.jetbrains.com/issue/CMP-9390/iOS-seems-to-ignore-consumeWindowInsets

[Chrimaeon]

Why using a very old alpha version. Navigation 3 went stable beginning of December https://developer.android.com/jetpack/androidx/releases/navigation3

[Kevin van Mierlo]

@Chrimaeon Yes, it went stable for Android, not for Compose Multiplatform. As far as I know, this is the newest version for Compose Multiplatform