iOS: LazyColumn scroll bug

[Caij]

Describe the bug
During scrolling, LazyColumn suddenly scrolls to the top, only on the iOS platform; there are no issues on the Android platform.

Affected platforms
Select one of the platforms below:

• All

Versions

• Kotlin version*: 1.9.0
• Compose Multiplatform version*: 1.4.3
• OS version(s)* (required for Desktop and iOS issues): iPhone 8 16.4

 val model by homeComponent.model.subscribeAsState()
    val rememberLazyListState = rememberLazyListState()
    LaunchedEffect(homeComponent) {
        homeComponent.init(object : Callback<Pair<Int, Int>> {
            override suspend fun onResult(t: Pair<Int, Int>) {

            }

            override fun onError(throwable: Throwable) {

            }
        })
    }
    LazyColumn(modifier = Modifier.fillMaxSize(), contentPadding = PaddingValues(top = paddingTop),
        state = rememberLazyListState) {
        itemsIndexed(model.tweets) { index, item ->
            AllTypeCardItemContent(item)
        }
    }

RPReplay_Final1693039855.MP4

Untitled.mp4

[elijah-semyonov]

Hi, it's known and worked on currently.
Duplicate of #3335

[Caij]

@elijah-semyonov Is this fixed in version 1.5.0 release?

[elijah-semyonov]

No, it will be fixed in a later patch after this PR is merged.

[Caij]

@elijah-semyonov I'm very sorry to bother you, but I would like to inquire about the timeline for addressing this issue. Many of my app users have reported this problem.

[elijah-semyonov]

@Caij you don't bother me at all, right now the solution for this issue in PR I've linked is partly a workaround for some bugs introduced in a mechanism called synthetic events. Doing it properly without workarounds and creating regressions could take some time, because it requires some internal discussion and all targets are using this mechanism.

Compose Multiplatform for Compose is in Alpha now, so issues like that are expected and we really value your feedback and reports which helps us to solve them.

I can't give you an accurate timeline, because there are quite some moving parts, but if it's a dire issue affecting you in long term, you could build compose locally from this repo, cherry pick PR above and ship your app with locally built compose. It will be probably accompanied with other bugs introduced by us between the release and jb-main HEAD, but it's the best we can do for now.

Watch the status of this PR (and related PRs if any) and follow us on social platforms to see if it's included in the update to come or not.