java.lang.IncompatibleClassChangeError #726
Comments
|
Any ideas how to fix/omit this problem. I have been reading about this issue and it looks it is realted to Annotations handling on Android 5+ devices (mostly Samsung). |
|
Did you upgrade to Gson 2.4? Try downgrading to Gson 2.3.1 and see if that fixes the problem. |
|
Actually I had version 2.2.4. Is it still a case? |
|
No, in that case, it is some other issue. |
|
No action for us to take here. |
|
Any hints there? Any ideas how to omit this? Maybe different version of Android annotation from V4 library? |
|
That seems a stretch, our app uses Gson and annotation processing and does On Mon, Nov 23, 2015 at 12:33 PM Dominik Tomczak notifications@github.com
|
|
Really odd. I can see on my error console growing number of that exceptions. (Jackson) I use Eclipse, Android 23 (6.0 SDK) as build SDK and latest v4/v7 libraries. I don't add special proguard file, it is a default one. Thanks |
|
I digged into this issue. It happens with any annotation class with a "value" method in it. SerializedName it is or other. |
|
I'm from Optimizely, and we have some clients who are seeing this issue as well. Is this something that can be fixed? |
|
We did some research and patched gson to make sure that the annotation would not use Turns out that this ended up causing crashes too, so the problem is not with the annotation using The new crash we get: TL;DR the problem is not with the annotation using |
|
Likely a build tools problem. Using ProGuard or similar? Those tools wreck your code. |
|
I turned off ProGuard but it's still a problem. It's all affected Samsung 5.0 Devices |
|
It looks like only Samsung Android 5 devices have this issue indeed
|
|
We are also seeing this crash with gson 2.3.1 on Android 5 on Samsung.
|
|
Anyone got a fix for this? I am also facing this issue. |
|
Im also getting this error in Samsung device when users update app from play store. Please check below log. |
|
Is the same error? |
|
I've got the same issue here and using 2.6.2. Again Samsung devices on Android 5:
|
|
I just update to 2.2.4 ,then solve this problem , but I don not know why ? |
|
Why is this issue closed? Was the resolution to rename all "value" keys? |
|
Still getting these crashed on Samsung Android 5.0.1 devices |
|
Any workaround? |
|
Using gson 2.8.0 and still have the problem |
|
+1 |
|
Same thing here. Has anyone found a workaround for this?
|
|
Did anyone find a workaround for this? |
|
This is constantly crashing our clients apps. While it only happens on a limited set of devices, it still makes up for more than 90% of our crashes. |
|
We are also facing this issue for Android 5 only, did anyone find any solution for this ?
|
|
3 years later and this still happening with our app on Android 5 Samsung devices also! |
|
Using Gson 2.8.5 and still experiencing the issue for Samsung lollipop devices. that's ridiculous. |
|
+1 |
|
+1 Also seeing on 5.0 Lollipop Samsung. Silly question, but I suppose removing the annotations and making the POJO field names match the JSON will make the bad man go away? |
|
@davros1970 I no longer work in the project where we had this issue, but I remember that we tried absolutely everything to get rid of this bug. If this bug is really annoying you the best thing is to try to move to another JSON parsing library. |
|
Any updates on this? |
|
I'm keep getting crashes on Samsung Galaxy Note 3 - Android 5.0: It looks like it can't convert to String Json if the class contains List or Object. This is how the parsing made: And this is the Product model object: As I said, I think the exception is thrown because the class contains another reference to another object. In my case is User |
|
I have too many crashes with Gson 2.8.1 only on Android 5 Samsung devices. Isn't there any solution for this issue yet?? |
|
I am also facing the same issue only on Samsung 5.0 devices. |
|
After 4 Years, We are still facing the same crash and the sad part is we haven't got the fix and the Issue is in Closed state. |
|
@morerohit86 If we wait 3,4 years more maybe Android 5 gonna get outdated and the issue will fix itself ¯_(ツ)_/¯ |
Is there any workaround for this problem? |
…ldsSummary Summary: PROBLEM ------- This constitutes 89.2% of overall ComponentUtils.hasEquivalentFields crashes in production. This is a known error which exists in Android Lollypop which was fixed in later OS versions. Details of the issue which was reported to Google : https://issuetracker.google.com/issues/37045084 google/gson#726 To summarise, libraries which uses annotations is facing this intermittently. Google closed this saying it is infeasible to fix this in older OS versions. Reviewed By: astreet Differential Revision: D19835819 fbshipit-source-id: cebef218bd97531d8892e31e8d40654edaaa97de
|
Hi also have such crash. Any workaround ? |
|
Still have this crash, waiting for 5 to deprecate, so, it must be the only way to fix it :`( |
7 years later and this still happening with our app on Android 14 Vivo devices also! |
|
As mentioned originally in #726 (comment), this is an issue with Android itself, see https://issuetracker.google.com/issues/37045084, and affected more than just Gson as also mentioned in some of the comments here. I assume that was why this Gson issue was closed because most likely there is nothing which can be done by Gson to fix this issue, instead this had to be fixed in the Android OS. @quibbler01, the situation might be the same for you. Maybe try contacting Vivo first (or reporting it on the Android bug tracker; not sure what the correct procedure is) and then please report here back. |
eamonnmcmanus
added
the
android
and others
I'm getting this crash lately. It complains about SerializedName class missing the "value" method.
This is the stacktrace:
The text was updated successfully, but these errors were encountered: