How would I scroll to an item in a lazy list by key? I don’t have the item index unfortunately. My current (bad) idea I’m toying with is copying the entirety of

LazyListState.animateScrollToItem

and making _modifications_™️ but that method will take me a ‘minute’ to understand enough to update.

Hello! I’m getting the following output and

java.lang.AssertionError

when using Asserts with kotlin

2.1.0-RC

or

2.1.0-RC2

. If I downgrade to

2.0.21

it works:

e: .gradle/caches/modules-2/files-2.1/org.jetbrains.kotlin/kotlin-stdlib/2.1.0-RC2/a2fc741252a95c0b35b2f6803cc4593751adc78f/kotlin-stdlib-2.1.0-RC2.jar!/META-INF/kotlin-stdlib-jdk7.kotlin_moduleModule was compiled with an incompatible version of Kotlin. The binary version of its metadata is 2.1.0, expected version is 1.9.0.
e: .gradle/caches/modules-2/files-2.1/org.jetbrains.kotlin/kotlin-stdlib/2.1.0-RC2/a2fc741252a95c0b35b2f6803cc4593751adc78f/kotlin-stdlib-2.1.0-RC2.jar!/META-INF/kotlin-stdlib-jdk8.kotlin_moduleModule was compiled with an incompatible version of Kotlin. The binary version of its metadata is 2.1.0, expected version is 1.9.0.
e: .gradle/caches/modules-2/files-2.1/org.jetbrains.kotlin/kotlin-stdlib/2.1.0-RC2/a2fc741252a95c0b35b2f6803cc4593751adc78f/kotlin-stdlib-2.1.0-RC2.jar!/META-INF/kotlin-stdlib.kotlin_moduleModule was compiled with an incompatible version of Kotlin. The binary version of its metadata is 2.1.0, expected version is 1.9.0.
e: .gradle/caches/modules-2/files-2.1/org.jetbrains.kotlin/kotlin-test-junit/2.1.0-RC2/b93d3ae5bf5d6705f0a7e996ae76625be9aab838/kotlin-test-junit-2.1.0-RC2.jar!/META-INF/kotlin-test_JUnit.kotlin_moduleModule was compiled with an incompatible version of Kotlin. The binary version of its metadata is 2.1.0, expected version is 1.9.0.
e: .gradle/caches/modules-2/files-2.1/org.jetbrains.kotlin/kotlin-test/2.1.0-RC2/589f4d86f57a00236e6af14e85e84f043ca7e41f/kotlin-test-2.1.0-RC2.jar!/META-INF/kotlin-test.kotlin_moduleModule was compiled with an incompatible version of Kotlin. The binary version of its metadata is 2.1.0, expected version is 1.9.0.

Can someone elucidate me? Thanks!

I'm having the same error after upgrading several of my projects to kotlin 2.0.0 for all native targets:

w: KLIB resolver: The same 'unique_name=org.jetbrains.kotlinx:atomicfu' found in more than one library: /home/nick/.gradle/caches/modules-2/files-2.1/org.jetbrains.kotlinx/atomicfu-linuxx64/0.20.2/6ad420ede07f27d1faff29de57851048afe77474/atomicfu.klib, /home/nick/.gradle/caches/modules-2/files-2.1/org.jetbrains.kotlinx/atomicfu-linuxx64/0.23.1/8c5db273962e5bee0c7cafb5c2e77aba595e0a3c/atomicfu.klib
w: KLIB resolver: The same 'unique_name=org.jetbrains.kotlinx:atomicfu-cinterop-interop' found in more than one library: /home/nick/.gradle/caches/modules-2/files-2.1/org.jetbrains.kotlinx/atomicfu-linuxx64/0.20.2/8cda96bf87ece8377d6307f8145182e9c46d226c/atomicfu-cinterop-interop.klib, /home/nick/.gradle/caches/modules-2/files-2.1/org.jetbrains.kotlinx/atomicfu-linuxx64/0.23.1/d44a87a9f79f578e7b36a853477cb61e794d6b74/atomicfu-cinterop-interop.klib
w: KLIB resolver: The same 'unique_name=org.jetbrains.kotlinx:kotlinx-coroutines-core' found in more than one library: /home/nick/.gradle/caches/modules-2/files-2.1/org.jetbrains.kotlinx/kotlinx-coroutines-core-linuxx64/1.7.1/b465f13ffe74e2d4d2b8448839e2ee6275f67fda/kotlinx-coroutines-core.klib, /home/nick/.gradle/caches/modules-2/files-2.1/org.jetbrains.kotlinx/kotlinx-coroutines-core-linuxx64/1.8.1/6cd5eda771c30c4e76ee7bc56f43051836e51b4d/kotlinx-coroutines-core.klib

Is there a way to get ByteArray/UIImage from Compose ImageBitmap for KMM iOS?

I’m working on a Compose app that lets users switch between dark, light and system default themes. Currently I’m having a problem where if the user selects the dark theme, the resources I have in the

drawable-night

resource set are not used, and instead the regular

drawable

resources are used, which leads to a very weird-looking UI. I know I can inform the system of the selected theme by doing either

UiModeManager.setApplicationNightMode()

or

AppCompatDelegate.setDefaultNightMode()

, and it seems to work, but for some reason it breaks the theme change when the users selects the system default option. Are there additional considerations for doing this in Compose that I’m missing?

How can we call WebView.destroy() within Compose? When using AndroidView+WebView. Does it even matter?

Hi, can SKIE handle Kotlin Result<T> type in a way to handle it on Swift side like this:

someResult.onSuccess { }.onFailure { }

I have an issue where engineers are not realizing coroutines are being used from a unit test so they do not add runTest. But then a later unrelated test has runTest will then throw these exceptions. So it causes some chaos around someone adding run test and then it causes other errors. Also tests with coroutine failures are sometimes being merged. Obviously the solution is use runTest when you are using coroutines but is there architectures or paths you have found to prevent these errors from accidentally being merged and secondly to keep the tests isolated so you get errors related to the test that is actually in failure rather than an unrelated test.

What’s the latest state of (shared) navigation for KMM? Anyone very happy with anything else then Decompose?

I'm using timepickerstate and datepickerstate for TimePicker and datepicker. I'm initializing them with default values (current time and current date). I'm then updating time and date in the ViewModel. In my composable, after they've been updated in the ViewModel, the picker dialogs don't reflect the new values, but are set to the initial values despite using

rememberTimePicker

and

rememberDatePicker

, respectively. To make date reflect new chosen date by user, I've to manually do a LaunchedEffect on the date (as stored in the ViewModel) and update the DatePickerState accordingly. However, TimePickerState does not have a way to update the time. Has anyone else ran into this and if so, how did you work around it?