Is this necessary for interop with some existing Android APIs? Nope, I don't know such APIs. You right, you can use@Serializableeverywhere, but not so good if you want to migrate to kotlinx.serialization some existing project (our case). ...
Invalid owner on line 383: /plugins/parcelize/ "Kotlin Compiler Core" Invalid owner on line 384: /plugins/pill/ Yan.Zhulanow "Kotlin Build Infrastructure" Invalid owner on line 385: /plugins/power-assert/ "Kotlin Compiler Core" Invalid owner on line 386: /plugins/sam-with-receiver/ ...
at java.desktop/java.awt.EventDispatchThread.run(EventDispatchThread.java:90) Caused by: java.util.concurrent.CompletionException: java.lang.RuntimeException: Resource not found: idea/ApplicationInfo.xml at java.base/java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:31...
plugins { id("com.android.application") id("dagger.hilt.android.plugin") kotlin("android") kotlin("kapt") id("kotlin-parcelize") id("kotlinx-serialization") } :network plugins { id("com.android.library") id("dagger.hilt.android.plugin") kotlin("android") kotlin("kapt") id("kotlin-...