Fixed
Status Update
Comments
vi...@google.com <vi...@google.com>
tn...@google.com <tn...@google.com> #2
I think this behavior is tied behind a flag to D8. Jerome and/or Mads, can you confirm that as of 4.1, you're passing --force-enable-assertions to D8/R8?
tn...@google.com <tn...@google.com> #3
(I quickly grepped the source code for AGP and didn't see it, but maybe it doesn't appear as that literal string or uses some constant defined by R8 somewhere.)
ag...@google.com <ag...@google.com> #5
Yes, as
tn...@google.com <tn...@google.com> #6
Thanks! This is now fixed in 4.2 and main. In 4.2, the check is just disabled by default. In main, it's deleted (along with more graceful handling, e.g. such that it doesn't complain about unknown issue id's left in build.gradle files, properly ignores these entries in basefiles, etc.)
Description
IMPORTANT: Please readhttps://developer.android.com/studio/report-bugs.html carefully and supply
all required information.
Studio Build: 4.1
Version of Gradle Plugin: 4.1
Version of Gradle: 6.6
Version of Java: 1.8
OS: All
Since AGP 4.1,
https://jakewharton.com/d8-optimization-assertions/#tomorrows-behavior
assert()
is working properly because of D8 behavior change.But lint checker still warn with old behavior with following message.
Please disable
AssertDetector
that can provide misleading help.