Is it something known? When using ProGuard with De...
# decompose
o
Is it something known? When using ProGuard with Decompose 2.0.1 and Compose 1.5.0 I got There were API breaking changes in Compose 1.5.0 related to
Pager
Copy code
Warning: com.arkivanov.decompose.extensions.compose.jetbrains.pages.ComposableSingletons$PagesKt$lambda-1$1: can't find referenced method 'void HorizontalPager-AlbwjTQ(int,androidx.compose.ui.Modifier,androidx.compose.foundation.pager.PagerState,androidx.compose.foundation.layout.PaddingValues,androidx.compose.foundation.pager.PageSize,int,float,androidx.compose.ui.Alignment$Vertical,androidx.compose.foundation.gestures.snapping.SnapFlingBehavior,boolean,boolean,kotlin.jvm.functions.Function1,androidx.compose.ui.input.nestedscroll.NestedScrollConnection,kotlin.jvm.functions.Function3,androidx.compose.runtime.Composer,int,int,int)' in program class androidx.compose.foundation.pager.PagerKt
For the record, the warning is in fact an error and fails the build which seems legit here. (
./gradlew runReleaseDistributable
)
a
That was a breaking API change in Compose 1.5.0 in Pager, indeed. So if you use
Pages
Composable function, you will have a runtime crash. Not sure why build fails, though. If you are not using
Pages
, it should be safe to suppress that error (if possible).
o
Maybe I didn't test the screen using the
Pager
code. When updating to Compose 1.5.0, I only had to change the call to the scroll state which was not compiling. Maybe, under the hood, the
Pager
code I use uses
Pages
, I'll check that tomorrow. Do you have plans to deliver a Decompose build compatible with Compose 1.5.0? (Obviously no pressure! Just to determine what should I do in short timeframe, wait for Decompose update or stay on Compose 1.4.x)
a
But no stable release yet
👌 1
o
FYI, my usage of
HorizontalPager
and
rememberPagerState
works in debug with Decompose
2.0.1
and Compose
1.5.0
but ProGuard fails like mentioned. I'm only using these API from the Pager feature. Using Decompose
2.1.0-alpha-07
with Compose
1.5.0
works as well and fixes the ProGuard issue in release builds.
👍 1