Amazon Device Messeging (ADM) 1.1.0 IncompatibleClassChangeError Exception - sdk

Question

After I apply the 1.1.0 adm to our app, some devices crash by the exception "java.lang.IncompatibleClassChangeError"
I cannot reproduce this error on the some Fire devices,
but the crash report says so.
I applied the the gradle setting from the manual.
so the adm jar was not included in the apk, I think so.
compileOnly files('libs/amazon-device-messaging-1.1.0.jar')
not all the device, but Sepcially the Fire 7 2019, Fire hd 8 2018 are the major crashed devices.
Here is the detail crash log
Fatal Exception: java.lang.IncompatibleClassChangeError: Structural change of com.amazon.device.messaging.ADMMessageReceiver is hazardous (/data/app/com.xxxx-1/oat/arm/base.odex at compile time, /system/priv-app/DeviceMessagingAndroidSDK/oat/arm/DeviceMessagingAndroidSDK.odex at runtime): Instance field count off: 0 vs 3
Lcom/amazon/device/messaging/ADMMessageReceiver; (Compile time):
Static fields:
Instance fields:
Direct methods:
<init>()V
<init>(Ljava/lang/Class;)V
<init>(Ljava/lang/Class;I)V
Virtual methods:
onReceive(Landroid/content/Context;Landroid/content/Intent;)V
registerIntentServiceClass(Ljava/lang/Class;)V
registerJobServiceClass(Ljava/lang/Class;I)V
Lcom/amazon/device/messaging/ADMMessageReceiver; (Runtime):
Static fields:
Instance fields:
I mJobId
Z mServiceClassIsJob
Ljava/lang/String; mServiceClassName
Direct methods:
<init>()V
<init>(Ljava/lang/Class;)V
<init>(Ljava/lang/Class;I)V
Virtual methods:
onReceive(Landroid/content/Context;Landroid/content/Intent;)V
registerIntentServiceClass(Ljava/lang/Class;)V
registerJobServiceClass(Ljava/lang/Class;I)V
(declaration of 'com.xxxx.adm.ADMReceiver' appears in /data/app/com.xxxx-1/base.apk)

Answer 1

We have resolved the issue.
It's because of the missed configuration in the build.gradle.
compile fileTree(include: ['*.jar'], dir: 'libs')
...
compileOnly files('libs/amazon-device-messaging-1.1.0.jar')
We used the same libs directory for the ADM,
so the stubed jar was included in the game apk.
The configuration compile fileTree(include: ['*.jar'], dir: 'libs') caused the issue.
We changed the adm jar's directory from libs to libs2 and that has solved the problem.