Luis Ramos

Thanks for the response! I've tried to figure it out, but my pearl skills are lacking. I'll update this if I find out the issue.

We were using "Whole module optimisation" in our debug builds, and had to turn it off because it was messing with our debugging. But I didn't test Injection after that....

Probably I should not be doing this, since now I get this error on app start: ``` objc[4634]: Class Bugsnag is implemented in both /private/var/containers/Bundle/Application/EB668D5F-6FF9-4C5E-AE93-3E402F090791/MyApp.app/Frameworks/shared.framework/shared (0x1060a8a68) and /private/var/containers/Bundle/Application/EB668D5F-6FF9-4C5E-AE93-3E402F090791/MyApp.app/MyApp (0x102b1ec68). One...

I can confirm that the previous solution corrects the bug, thanks for that.

@griffio could you give an example of "Manual json serialization appears to solve the issue - have tried it"? I would love to get the plugin working, but I keeping...

In [kotlinx.serialization/CHANGELOG.md](https://github.com/Kotlin/kotlinx.serialization/blob/master/CHANGELOG.md) > you can use this 1.9.0 kotlinx-serialization version (Kotlin 2.2 is required). In #5975 @JakeWharton replaced moshi with kotlinx.serialization, but left the `exclude group: "org.jetbrains.kotlin"` in the `runtimeClasspath`....

Thank you @griffio, the stdlib patched plugin stopped throwing the loader constraint violation error for me (Android Studio Otter | 2025.2.1 Patch 1 and SQLDelight 2.2.1), but the banner "SQLDelight...