IssueTracker

Thanks for the report.

If you can provide a compiler input dump of the project in private with zerny@google.com that would allow us to reproduce the issue locally. If not, it might be possible for us to gather info from the class files for io.netty.handler.codec.DefaultHeaders and io.netty.util.HashingStrategy if you can share those.

FYI, retraced stack is:

at com.android.tools.r8.internal.gg.a(SourceFile:376)	
=>
at com.android.tools.r8.ir.optimize.classinliner.InlineCandidateProcessor.removeMiscUsages(InlineCandidateProcessor.java:650)	
at com.android.tools.r8.ir.optimize.classinliner.InlineCandidateProcessor.processInlining(InlineCandidateProcessor.java:388)	

I'll provide the information asap.

Another data point is that version 3.0.43 also has the same issue.

I've shared it directly with you and SG.

Thanks for the dump! I can confirm that it reproduces locally. I'll post back as soon as I have more info.

Minor update. This issue reproduces on main. The cause is a class inlining of a statically known inner class. The class inliner identifies what appears to be a correct inlining candidate, but the forced method inline does not take place. It is still not clear why the method inlining does not take place.

Thanks for the update!

QQ: When you find a fix for it, will that be applied on the 3.0 branch too?

Yes, I intend to backport the fix to 3.0 if possible.

A fix has landed for this issue on our branches. You can enable the 3.0.73 locally by amending your top-level build.gradle file with:

buildscript {
    repositories {
        maven {
            url 'https://storage.googleapis.com/r8-releases/raw'
        }
    }
    dependencies {
        classpath 'com.android.tools:r8:3.0.73'          // Must be before the Gradle Plugin for Android.
        classpath 'com.android.tools.build:gradle:X.Y.Z' // Your current AGP version.
     }
}

I've verified that the provided dump compiles with this version. Let us know if the same is true on your end.

Thank you very much, I can confirm it works as intended and it ran successfully on our project!

Good to hear. Thank you for reporting and for the reproduction!

Thank you for your patience while our engineering team worked to resolve this issue. A fix for this issue is now available in:

• Android Studio Bumblebee Canary 13 (2021.1.1.13)
• Android Gradle Plugin 7.1.0-alpha13

We encourage you to try the latest update.

If you notice further issues or have questions, please file a new bug report.

Thank you for taking the time to submit feedback — we really appreciate it!