Status Update
Comments
ru...@gmail.com <ru...@gmail.com> #2
Submitter:
Can you please provide a brief text explanation of:
- What is the summary of the issue you're seeing
- What is the expected behavior
- What is the actual behavior
- What software is showing the bug. What version of software are you reporting it against
- What operating system are you running (android version, device)
- If an app integration, what version of emojicompat or emoji2 are you linking against.
Thanks!
Description
Version used: 2.3.2
Caused by:
- NavHostFragment looks up a DialogFragmentNavigator in "onAttachFragment" and no null check is done
- A custom Dialog fragment navigator can't extend from DialogFragmentNavigator as it's a final class
Commit that introduced this:
Can the new API be used instead to fix this issue in the next alpha/beta release?
In alternative, do you suggest other workaround or should we wait and stay in 2.3.1 until this is fixed?