Fixed
Status Update
Comments
il...@google.com <il...@google.com>
il...@google.com <il...@google.com> #2
Hey, I would like to take this up?
mh...@google.com <mh...@google.com> #3
Hey, any help on how can I proceed forward.?
ap...@google.com <ap...@google.com> #4
Re #2,3 - We've just published our
Fragment have some existing lint checks in their fragment-lint
project, so some of the steps are already taken care of for you (and the existing Lint checks are a good place to look for code examples and testing strategies).
Thanks for offering to help!
jb...@google.com <jb...@google.com> #5
jo...@gmail.com <jo...@gmail.com> #6
Thank you for the pull request! This has been added internally and will be a part of the next Fragment alpha release.
il...@google.com <il...@google.com> #7
I know the ticket is closed but ..
if you call getLayoutInflater from onCreate method (not onCreateDialog) you may have a crash.
because getLayoutInflator goes to onGetLayoutInflater and then it can go to onCreateDialog (even though the entry point is onCreate dialog)
if you call getLayoutInflater from onCreate method (not onCreateDialog) you may have a crash.
because getLayoutInflator goes to onGetLayoutInflater and then it can go to onCreateDialog (even though the entry point is onCreate dialog)
de...@gmail.com <de...@gmail.com> #8
Comment has been deleted.
de...@gmail.com <de...@gmail.com> #9
Still getting this annoying lint error. For some reason this probably happens after updating to AGP 7.4.0-alpha03. The error is pointing to DaggerApplication which is even more confusing
Description
Component used: Fragment Version used: (latest 1.4.0-SNAPSHOT) Devices/Android versions reproduced on: N/A (host lint crash)
A new lint check was added to androidx.fragment ( DialogFragmentCallbacksDetector ) which is crashing lint when run. It looks like it crashes if a javafile has a class/interface with no supertype?
Here is an abridged stacktrace: