anyone had "`Debug information is inconsistent`" bug with Intellij while in debug mode?

Noticed that Accompanist-Glide library is now deprecated (as of v0.14), had some questions around this: • Why was this done? Is Coil the recommended official solution? • For existing Android Views that use Glide, is Glide -> Coil migration now a pre-requisite of Android View -> Compose migration?

Does anyone know if there is a recommended way to unit test SQLDelight common code on Android? You need an android context for the sql driver. Should I use instrumented unit tests or Roboelectric? Is there some other better way?

Hey guys, has anyone figured out how to use ComposeResources in

@Preview

in androidMain module? Even though I specify in my

build.gradle

in the

android

block this:

sourceSets["main"].apply {
    manifest.srcFile("src/androidMain/AndroidManifest.xml")
    resources.srcDirs("src/commonMain/composeResources")
}

it still gives an exception:

org.jetbrains.compose.resources.MissingResourceException: Missing resource with path: values/strings.xml

Please note, that it works as it should when I launch the app on Android

Do Android Compose Previews work for anyone in the IntelliJ? We are using Android and Compose plugins with IntelliJ IDEA 2023.3.4 and we don't see Compose previews at all - there are no

Code | Split | Design

options nor gutter preview icon, like the ones you would see in Android Studio. They seem to work with our setup in Android Studio but we are using IJ due to certain performance issues with AS.

I'm trying to hide the system bars in a compose app, and it works well until I need show a popup. When the popup is shown, it shows the system bar. If

PopupProperties(dismissOnBackPress = false)

is passed then it shows the bar briefly. Sample in 🧵

Found it! Just write the exact same file twice in ksp and it breaks :kspKotlinMetadata

withContext

is throwing null pointer exception in my code. This seems like a new issue, never faced this before. Using Micronaut 3.1.0, Kotlin 1.5.31, kotlin-runtime 3.1.0

What is the proper Kotlin Flow alternative to SingleLiveEvent?

Doesn't kotlinx.coroutines support true multi-threading on WASM target ? I know it's experimental but it's an interesting WIP It seems wasm introduced atomic operations to lay the groundwork for true multhreading but it's apparently not rolled out or stable on all browsers ? or is it already there with all android-like dispatchers and true multithreading support instead of some scheduling magic on a single thread at the end of the day.

While Dispatchers.Default and Dispatchers.IO are supported in Kotlin's coroutine model, their behavior on WASM is constrained by the current state of WebAssembly's threading support. These dispatchers typically rely on background threads or thread pools to offload tasks, but in WASM, where true multithreading is still experimental and not universally supported, these dispatchers will operate in a similar way to Dispatchers.Main, running tasks on the same main thread.

It almost sounds like what we're seeing here is a sophisticated scheduling optimization found precisely in Javascript target, which is constrained obviously by javascript's 1 main thread restriction. Right ? edit: found on rust forums that WASM Threads are released for chrome already with atomic ops and

SharedArrayBuffer

! but not for other browsers 🤔