Component used: Fragment
Version used: 1.2.0-rc03
Devices/Android versions reproduced on:
- Pixel 3 API 27 Emulator
- Pixel 3 API 29 Emulator
- LG G7 ThinQ API 28

Sample code: https://github.com/eneim/Fragment-RC3-Bug

How to use:
- Make sure Fragment F1 is using layout fragment_f1_bad. Use the code to start the MainActivity, produce a configuration change (eg: rotate the device) --> it will crash due to an Exception is thrown in a check code.
- Changing F1 layout to fragment_f1_good and it will be fine.

Description:

- Saying I have a Fragment F1 in my Activity, defined either by xml (fragment tag or FragmentContainerView) or manual adding at runtime.
- F1's layout is defined in an xml with a 'fragment' tag whose name is a Fragment F2.
- The app starts normally as usual.
- If a configuration change happens, the destruction of F1 will call F2's onViewCreated.

In the sample app, I put a check code which checks if the Activity is destroyed or not, and in this case it will crash the app.

The expected behavior should be: the destruction of F1 should not call F2's onViewCreated.

This issue doesn't occur on 1.2.0-rc03 IF I use `FragmentContainerView` instead of `fragment` to add F2.
This issue cannot be reproduced on 1.2.0-rc02, 1.2.0-rc01 and (I believe) earlier versions.

Please find a call stack in attached screenshot (taken from a debug session on Pixel 3 API 29 Emulator).

Issue 146290333

Mentioned issues (1)

Links (8)

Issue metadata