kochavaFAA android error - only after first install

Hello,

It is only happening after first install from play store, it is not happening if you install apk directly or second run;

Here is the error report from ANR & Crashes from play console.

java.lang.RuntimeException: Unable to instantiate receiver com.kochava.android.tracker.ReferralCapture: java.lang.ClassNotFoundException: Didn’t find class “com.kochava.android.tracker.ReferralCapture” on path: DexPathList[[zip file “/data/app/*****/base.apk”],nativeLibraryDirectories=[/data/app/*****/lib/arm, /data/app/*****/base.apk!/lib/armeabi-v7a, /system/lib, /vendor/lib]]

at android.app.ActivityThread.handleReceiver(ActivityThread.java:3021)

at android.app.ActivityThread.-wrap18(ActivityThread.java)

at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1561)

at android.os.Handler.dispatchMessage(Handler.java:102)

at android.os.Looper.loop(Looper.java:154)

at android.app.ActivityThread.main(ActivityThread.java:6119)

at java.lang.reflect.Method.invoke(Native Method)

at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:886)

at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:776)

Caused by: java.lang.ClassNotFoundException: Didn’t find class “com.kochava.android.tracker.ReferralCapture” on path: DexPathList[[zip file “/data/app/*****/base.apk”],nativeLibraryDirectories=[/data/app/*****/lib/arm, /data/app/*****/base.apk!/lib/armeabi-v7a, /system/lib, /vendor/lib]]

at dalvik.system.BaseDexClassLoader.findClass(BaseDexClassLoader.java:56)

at java.lang.ClassLoader.loadClass(ClassLoader.java:380)

at java.lang.ClassLoader.loadClass(ClassLoader.java:312)

at android.app.ActivityThread.handleReceiver(ActivityThread.java:3016)

… 8 more

@bulupe

I’ll have a look to see what’s going on…

@bulupe

There was a typo in the plugin’s manifest that prevented the correct receiver name to be used.

It has been fixed and is live on our build servers now.

Thank you @ingemar_cl

@bulupe

I’ll have a look to see what’s going on…

@bulupe

There was a typo in the plugin’s manifest that prevented the correct receiver name to be used.

It has been fixed and is live on our build servers now.

Thank you @ingemar_cl