Fixed
Status Update
Comments
il...@google.com <il...@google.com>
sa...@google.com <sa...@google.com>
sa...@google.com <sa...@google.com>
ap...@google.com <ap...@google.com> #2
Please provide a minimal sample project that reproduces this issue.
ap...@google.com <ap...@google.com> #3
Sure, I created a minimal sample app for you:
Just click "Next Fragment" multiple times, then press the back button or perform the back gesture multiple times in quick succession.
Note: I tested this on a Pixel 8 with Android 14. Also, I have the predictive back animations enabled in the developer options.
sa...@google.com <sa...@google.com>
jb...@google.com <jb...@google.com> #4
Just FYI: Still happens on fragment library version 1.7.1
.
na...@google.com <na...@google.com> #5
Still crashing with fragment 1.8.0
. I have updated my example github repo with all latest libraries.
co...@gmail.com <co...@gmail.com> #6
Still crashing with fragment 1.8.1
. Example GitHub Repo was updated again.
Description
Version used: 1.5.1 (also tested on 1.7.0-alpha01)
Devices/Android versions reproduced on: Pixel 5 API 30 emulator
Description:
The linked repo or ZIP contains a reproduction of an issue with the AppCompatDialog & Componentdialog. It shows that the ComponentDialog does not set the ViewLifecycleTreeOwner correctly when setContentView is called. AppCompatDialog (the subclass of ComponentDialog) does not call super.setContentView and instead calls a delegate which never reaches ComponentDialog. When trying to access the ViewTreeLifecycleOwner of the dialog, a null pointer exception is thrown.
If this is a bug in the library, we would appreciate if you could attach:
-
- ZIP also attached