Assigned
Status Update
Comments
sg...@google.com <sg...@google.com> #2
I just attached a minimal test application with duplicated and multiline traces. Provided are a couple of logcat files and screenshots.
To me this isn'r really a big problem, since AS compiles my application and lets me debug it. That's what I use it for in my company. I just found it a bit annoying that something that worked one way in AS 2.x and 3.0, suddenly changed in 3.1. The new way results more time-consuming to me while debugging and reviewing the logs.
Could this be made configurable? Not necessarily in the UI, but editing some properties file. Thanks. :)
To me this isn'r really a big problem, since AS compiles my application and lets me debug it. That's what I use it for in my company. I just found it a bit annoying that something that worked one way in AS 2.x and 3.0, suddenly changed in 3.1. The new way results more time-consuming to me while debugging and reviewing the logs.
Could this be made configurable? Not necessarily in the UI, but editing some properties file. Thanks. :)
cl...@google.com <cl...@google.com> #3
I have the same problem.
be...@gmail.com <be...@gmail.com> #4
I also have the same problem.
Description
Please ensure that class is marked as '@serializable' and that the serialization compiler plugin is applied.
at kotlinx.serialization.SerializationException.(SerializationException.java:49)
at kotlinx.serialization.internal.Platform_commonKt.serializerNotRegistered(Platform_common.kt:91)
at kotlinx.serialization.SerializersKt__SerializersKt.serializer(SerializersKt__Serializers.kt:278)
at kotlinx.serialization.SerializersKt.serializer(Serializers.kt:1)
at androidx.navigation.NavDestinationBuilder.(NavDestinationBuilder.kt:91)
at androidx.navigation.compose.ComposeNavigatorDestinationBuilder.(ComposeNavigatorDestinationBuilder.kt:95)
When falling back to R8 8.3.xx (8.3.37/8.3.36), compilation doesn't fail.
Environment
Kotlin version: 2.0.0
Kotlinx serialization: 1.6.3
Gradle version: 8.7
Gradle plugin version: 8.6.1
Navigation: 2.8.0
Is there some new proguard rules to add ?