IssueTracker

Component used: Fragment Version used: 1.3.3 Devices/Android versions reproduced on: Emulator Android 10

Currently there is a crash trying to get parcelable from result after process restoration.

Setup:

• There is MainActivity, FirstFragment and SecondFragment.
• It is possible to navigate from FirstFragment to SecondFragment.
• FirstFragment calls getParentFragmentManager().setFragmentResultListener() in onViewCreated() and listens for result.
• SecondFragment calls getParentFragmentManager().setResult() on submit button click. Submit button does only that and doesn't navigate back to FirstFragment.
• Result is packed in Bundle via putParcelable(). We send back ExampleClass which implements Parcelable using @kotlinx.parcelize.Parcelize.

Steps to reproduce:

1. Launch application, navigate to SecondFragment.
2. Select something, click submit button, but don't navigate back.
3. Make process die, for example, using Developer Options -> Background Process Limit
4. Open process, navigate back
5. FirstFragment receives result in FragmentResultListener#onFragmentResult and calls result.getParcelable().
6. Application crashes with android.os.BadParcelableException

Stacktrace

There two ways to avoid crash:

1. Call result.setClassLoader(context.classLoader) before result.getParcelable().
2. Set result after state restoration again.

Is this something that should be fixed on Fragment or platform side?

What is the preferred workaround for the app developers in the meantime?