Difference between android.enableD8.desugaring in Android Studio 3.1 and android.enableD8

android android-studio android-gradle-plugin dex android-studio-3.1
0xAliHn picture 0xAliHn · Mar 28, 2018 · Viewed 7.9k times · Source

In Android Studio 3.0 there is an option android.enableD8 to enable D8 (Next-generation Dex Compiler). In Android Studio 3.1 a new option was added for this like android.enableD8.desugaring as per their updates.

What actually does android.enableD8.desugaring do in Android Studio 3.1 and what's the difference compared to the android.enableD8 option?

Answer

WoogieNoogie picture WoogieNoogie · Mar 28, 2018

The desugar step is executed normally after javac to optimize the bytecode. Enabling desugaring in D8 will remove that step entirely, and execute desugar as part of D8, making it faster and more optimized.

Source: https://android-developers.googleblog.com/2017/08/next-generation-dex-compiler-now-in.html

Related questions

Cannot fit requested classes in a single dex file, even for earlier commits which previously compiled fine

So I've just hit the maximum method count limit for my android project, which fails to build with the following error message: Error: null, Cannot fit requested classes in a single dex file (# methods: 117407 > 65536) I understand what the message …

Read More
Android Studios RuntimeException: Unexpected exception in dex writer thread

I have been getting this strange error the whole of today - anyone know what is going wrong here? As far as I know, I have been using the multidex library correctly (the below is from the app.gradle file): …

Read More
Android- Error:Execution failed for task ':app:transformClassesWithDexForRelease'

The Problem is that i am able to run my app when i change to debug mode but it fails when i switch to release mode. Exception: **FAILURE: Build failed with an exception.** > Execution failed for task ':app:…

Read More