Android release build crashes with proguard error

[abacaj]

This appears to be new as I have changed no code and was working 2 weeks ago... All i did was flutter upgrade.

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:transformClassesAndResourcesWithProguardForRelease'.
> Job failed, see logs for details

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

Flutter version:

[✓] Flutter (Channel master, v1.1.5-pre.38, on Mac OS X 10.13.6
    17G65, locale en-US)
    • Flutter version 1.1.5-pre.38 at /Users/anton/flutter
    • Framework revision b9f9e384cb (9 hours ago), 2019-01-01
      11:47:29 -0500
    • Engine revision b1a9a6e794
    • Dart version 2.1.1 (build 2.1.1-dev.0.1 88e6fe0f67)

[zoechi]

Can you reproduce in dev channel?

[ezraaaa]

I'm having the same problem too. I've tried dev channel and it is returning the same thing

[abacaj]

Yes tried all channels available, same result.

[remosingh]

same issue....

[zoechi]

As far as I understand Proguard is currently not fully supported.
I'm closing this as duplicate of #11099

[xiaoxiaocainiao]

try this one:
minifyEnabled false

[00011110]

@xiaoxiaocainiao thanks man, it works!

[00011110]

@xiaoxiaocainiao ， thanks man, it works!

[cfguimaraes]

@xiaoxiaocainiao that work for me too. Thank you.

In case some face this problem, the path to setting is android/app/build.gradle

[muammarridho]

@xiaoxiaocainiao it works, thanks bro.

[avvari-da]

If you are not intending to change minifyEnabled false, this worked fine for me - #19250 (comment)

[gitaaron]

Does this increase the size of the final binary?

[TobiCrackIT]

minifyEnabled false worked

[Nisthar]

Does this increase the size of the final binary?

Yes. i wish there was a way to fix this with minify enabled.

[WBlackstorm]

minifyEnabled false
shrinkResources false

Solved to me.

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.