You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a few stacktraces from Samsung 5.X devices that crash on attempt to read class annotations.
It's a known issue of Samsung firmwares (https://issuetracker.google.com/issues/37045084) and I know it's not Jackson issue.
Still, for some reason it wasn't present with GSON (or at least we didn't see it), and jackson-kotlin-module could, probably, have a graceful fallback for these crashes, fixing the problem for thousands of our users.
Caused by java.lang.IncompatibleClassChangeError: Couldn't find kotlin.Metadata.bv
at libcore.reflect.AnnotationAccess.toAnnotationInstance(AnnotationAccess.java:659)
at libcore.reflect.AnnotationAccess.annotationSetToAnnotations(AnnotationAccess.java:633)
at libcore.reflect.AnnotationAccess.getDeclaredAnnotations(AnnotationAccess.java:161)
at java.lang.Class.getDeclaredAnnotations(Class.java:891)
at com.fasterxml.jackson.module.kotlin.KotlinModuleKt.isKotlinClass(SourceFile:29)
and
Caused by java.lang.IncompatibleClassChangeError: Couldn't find kotlin.Metadata.k
at libcore.reflect.AnnotationAccess.toAnnotationInstance(AnnotationAccess.java:659)
at libcore.reflect.AnnotationAccess.annotationSetToAnnotations(AnnotationAccess.java:633)
at libcore.reflect.AnnotationAccess.getDeclaredAnnotations(AnnotationAccess.java:161)
at java.lang.Class.getDeclaredAnnotations(Class.java:891)
at com.fasterxml.jackson.databind.util.ClassUtil.findClassAnnotations(SourceFile:1072)
Any chance this exception could be caught by jackson with some graceful fallback provided? For example, class could be handled as if it doesn't have any annotations on it.
Thanks
The text was updated successfully, but these errors were encountered:
We have a few stacktraces from Samsung 5.X devices that crash on attempt to read class annotations.
It's a known issue of Samsung firmwares (https://issuetracker.google.com/issues/37045084) and I know it's not Jackson issue.
Still, for some reason it wasn't present with GSON (or at least we didn't see it), and jackson-kotlin-module could, probably, have a graceful fallback for these crashes, fixing the problem for thousands of our users.
Here is another related thread from Stackoverflow: https://stackoverflow.com/questions/29619052/how-to-fix-incompatibleclasschangeerror-during-android-jackson-parsing-using-ann/30355502#30355502
Here are some traces:
and
Any chance this exception could be caught by jackson with some graceful fallback provided? For example, class could be handled as if it doesn't have any annotations on it.
Thanks
The text was updated successfully, but these errors were encountered: