Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign up"Couldn't find outer class" with Proguard but not R8 #1754
Comments
Walll-E
commented
Feb 13, 2020
•
|
This looks like a bug in desugar, which you should file to Google. Can you provide details on the version of Gradle you used and its configuration, as well as the version of LeakCanary? Also ideally if you could reproduce this with a sample project and provide it, it would be helpful. Without all this information there's not much we can do. |
I have the same problemg . @pyricau |
|
Can you reproduce this with a sample project? |
|
Closing due to no response. Happy to take a look if someone can provide a sample project that reproduces this issue. |
|
I have the same issue with Proguard but with R8 everything is fine. unfortunately I can't use R8 yet |
|
Hi! I added this comment on #1354 and then I noticed that this issue is actually very similar to what happens to me. I'm upgrading from LeakCanary v1.6.3 to v2.3 and Proguard fails with some missing references: Edit from @pyricau: this was a long list of warnings which doesn't point to any actual error and made the issue harder to read so I removed it. Using R8 instead make it works ok. Hope it helps! |
|
This looks similar to arrow-kt/arrow#807 which was fixed by arrow-kt/arrow#926 and was apparently caused by https://youtrack.jetbrains.com/issue/KT-16084 The next steps here are to repro with https://github.com/roman-nevr/LeakCanaryFailSample and then change the failing code until the sample passes. |
|
@roman-nevr what command do you run to reproduce the failure? |
I choose |
|
@roman-nevr there is no |
|
I started looking into this but without the ability to repro there are simply too many nested lambdas, I can't go randomly poke at which lambdas to move. |

