Some users report ClassNotFoundException for launch activity <p>Some users are reporting a crash for my App which I cannot reproduce or even verify.</p> <pre><code>java.lang.RuntimeException: Unable to instantiate activity ComponentInfo{my.app/com.example.activity.SplashScreenActivity}: java.lang.ClassNotFoundException: Didn't find class "com.example.activity.SplashScreenActivity" on path: /mnt/asec/my.app-1/pkg.apk at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2219) at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2349) at android.app.ActivityThread.access$700(ActivityThread.java:159) at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1316) at android.os.Handler.dispatchMessage(Handler.java:99) at android.os.Looper.loop(Looper.java:176) at android.app.ActivityThread.main(ActivityThread.java:5419) at java.lang.reflect.Method.invokeNative(Native Method) at java.lang.reflect.Method.invoke(Method.java:525) at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1046) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:862) at dalvik.system.NativeStart.main(Native Method) Caused by: java.lang.ClassNotFoundException: Didn't find class "com.example.activity.SplashScreenActivity" on path: /mnt/asec/my.app-1/pkg.apk at dalvik.system.BaseDexClassLoader.findClass(BaseDexClassLoader.java:64) at java.lang.ClassLoader.loadClass(ClassLoader.java:501) at java.lang.ClassLoader.loadClass(ClassLoader.java:461) at android.app.Instrumentation.newActivity(Instrumentation.java:1078) at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2210) ... 11 more </code></pre> <p>My problem is I get some negative reviews from people who seem unable starting the App at all. I downloaded it on all my test devices from the Play Store and it ran fine.</p> <p>The systems reported to me where Android 4.1 (Huawei Phone), Android 4.3 (Galaxy S3) and Android 4.4 (Galaxy Note 2).</p> <p>I disassembled my apk and checked that the class is in fact contained, and referenced properly. And as previously mentioned, none of the devices available to me can reproduce the problem.</p>