Didn't find class "androidx.core.splashscreen.test.SplashScreenAppCompatTestActivity" [200312941]

Fixed

Bug

core-splashscreen

Status Update

No update yet.

Description

vs...@gmail.com

created issue #1

Sep 19, 2021 02:22PM

Artifact used: androidx.core:core-splashscreen:1.0.0-alpha01
Devices/Android versions reproduced on: Nexus 5X, Android 8.1.0

Recently I detected a couple of crashes (via Crashlytics) on production build using androidx.core:core-splashscreen:1.0.0-alpha01. I have no repros for these, just a stacktrace:

Fatal Exception: java.lang.RuntimeException: Unable to instantiate activity ComponentInfo{com.vsevolodganin.clicktrack/androidx.core.splashscreen.test.SplashScreenAppCompatTestActivity}: java.lang.ClassNotFoundException: Didn't find class "androidx.core.splashscreen.test.SplashScreenAppCompatTestActivity" on path: DexPathList[[zip file "/data/app/com.vsevolodganin.clicktrack-GQYmd9elNrX0UZIcCoRB4Q==/base.apk"],nativeLibraryDirectories=[/data/app/com.vsevolodganin.clicktrack-GQYmd9elNrX0UZIcCoRB4Q==/lib/x86, /system/lib, /vendor/lib]]
       at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2679)
       at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2856)
       at android.app.ActivityThread.-wrap11(ActivityThread.java)
       at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1589)
       at android.os.Handler.dispatchMessage(Handler.java:106)
       at android.os.Looper.loop(Looper.java:164)
       at android.app.ActivityThread.main(ActivityThread.java:6494)
       at java.lang.reflect.Method.invoke(Method.java)
       at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:438)
       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:807)
Caused by java.lang.ClassNotFoundException: Didn't find class "androidx.core.splashscreen.test.SplashScreenAppCompatTestActivity" on path: DexPathList[[zip file "/data/app/com.vsevolodganin.clicktrack-GQYmd9elNrX0UZIcCoRB4Q==/base.apk"],nativeLibraryDirectories=[/data/app/com.vsevolodganin.clicktrack-GQYmd9elNrX0UZIcCoRB4Q==/lib/x86, /system/lib, /vendor/lib]]
       at dalvik.system.BaseDexClassLoader.findClass(BaseDexClassLoader.java:125)
       at java.lang.ClassLoader.loadClass(ClassLoader.java:379)
       at java.lang.ClassLoader.loadClass(ClassLoader.java:312)
       at android.app.Instrumentation.newActivity(Instrumentation.java:1174)
       at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2669)
       at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2856)
       at android.app.ActivityThread.-wrap11(ActivityThread.java)
       at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1589)
       at android.os.Handler.dispatchMessage(Handler.java:106)
       at android.os.Looper.loop(Looper.java:164)
       at android.app.ActivityThread.main(ActivityThread.java:6494)
       at java.lang.reflect.Method.invoke(Method.java)
       at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:438)
       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:807)

There is no such class in library bundle indeed but it is present in AndroidManifest.xml in library aar. I cannot imagine in which reasonable scenario this could reproduce, but I think it's clear enough that this entry is redundant in manifest.

Comments

sj...@google.com <sj...@google.com> #2Sep 20, 2021 06:48PM

This actually has nothing to do with NavHostFragment, but is the behavior of NavController's setGraph().

When you call navController.setGraph(R.navigation.navigation_graph), it stores that ID and will restore that ID automatically.

If you were to instead use:

NavInflater navInflater = new NavInflater(this, navController.getNavigatorProvider());
navController.setGraph(navInflater.inflate(R.navigation.navigation_graph));

Then NavController would not restore the graph itself and the call to restoreState() you point out would only restore the back stack state, etc. but would wait for you to call setGraph again.

You're right that the inconsistency between the two setGraph methods is concerning. We'll take a look.

sj...@google.com <sj...@google.com> #3Sep 20, 2021 06:49PM

Assigned to bu...@google.com.

Turns out, we already had a tracking bug for this issue, will follow up on that other one.

bu...@google.com <bu...@google.com> #4Sep 20, 2021 06:49PM

Accepted by bu...@google.com.

Thank you for promptly replying to my report. You are right that the issue you've just mentioned is similar to mine. I shall continue observing the progress over there.

vs...@gmail.com <vs...@gmail.com> #5Sep 20, 2021 07:20PM

Oops, nevermind! I found out that this is fixed for alpha-02 by now in 79d69554ebbe8927f2d34af21f955606f858919a. Sorry for disturbance.

bu...@google.com <bu...@google.com> Sep 27, 2021 06:51PM

Status: New

sa...@google.com <sa...@google.com> Oct 4, 2021 06:49PM

Marked as fixed, reassigned to ca...@google.com.

Issue 200312941