IssueTracker

I found the root cause! The fragment savedstate class uses a null class loader. Come on, that's Android 101! The correct creator should be:
        public static final Parcelable.Creator<SavedState> CREATOR
                = new Parcelable.Creator<SavedState>() {
            @Override
            public SavedState createFromParcel(Parcel in) {
                return new SavedState(in, getClass().getClassLoader()); // <------
            }

            @Override
            public SavedState[] newArray(int size) {
                return new SavedState[size];
            }
        };

For wondering how to fix this, reflection will do the trick:
        // TODO https://issuetracker.google.com/issues/74354091
        val fragmentStateField: Field = Fragment.SavedState::class.java
                .getDeclaredField("mState").apply {
                    isAccessible = true
                }

            // ...
            (fragmentStateField.get(savedState) as Bundle).classLoader = javaClass.classLoader

Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:

Android bug report
After reproducing the issue, press the volume up, volume down, and power button simultaneously. This will capture a bug report on your device in the “bug reports” directory. Attach the bug report  file to this issue.

Alternate method:
After reproducing the issue, navigate to developer settings, ensure ‘USB debugging’ is enabled, then enable ‘Bug report shortcut’. To take bug report, hold the power button and select the ‘Take bug report’ option.

Please provide the information requested in comment #3 to investigate this issue further.

I think this a duplicate of https://issuetracker.google.com/issues/74607887 you can find more information there.

nabrozidhs@, can you please provide the android bug report to confirm that is duplicate or not.

Hi,
are there any news on this issue?
Thanks,
Matthias

I have the same issue. Not always reporting the failure on the same class, as above.

--full-stacktrace attached.

Please let me know if I can help further to resolve this.

I assume there is no workaround to this issue? Reverting my code to 1.7 without Jack is a very daunting prospect, but I need to produce an obfuscated release build...

I get the same error, always when running proguard, and always the RunnerProcessException classes are random which include classes besides the gms package

Same problem here.

Maybe we should read this??
https://developer.android.com/guide/platform/j8-jack.html

"The Jack toolchain is deprecated, as per this announcement. You may continue to use it, or try the latest preview version of Android Studio to use improved support for Java 8 language features built into the default toolchain."

Can we use java 8 without jack? I will try it out with AndroidStudio 3

As the Jack compiler toolchain has been deprecated for 2 years (see https://android-developers.googleblog.com/2017/03/future-of-java-8-language-feature.html) we are closing all Jack bugs.

Please reopen this bug if it reproduces using the latest stable D8/R8 compiler toolchain.