![]() Thankfully there’s a handy Gradle plugin which can help you work out whether or not you’re in a position to drop Jetifier, and point out the dependencies which are preventing you from doing so. What are the next steps? How do I check if I can disable it? So it’s clear that there’s some build performance gains to be had by disabling Jetifier. Jetifier also imposes a hit to Gradle’s configuration time - something that we’re already acutely aware of at Cuvva due to our large (150+) number of modules. That being said, this issue is marked as fixed in AGP 4.1.0-alpha01. Worse, the outputs of this transform step are not cacheable, resulting in slower incremental builds every single time and this all adds up over the course of many compilations during a typical work day. “Jetifiying” large dependencies can take a fair bit of time - perhaps a couple of seconds per binary. The downside: this is an extra build step in an already complex build pipeline. It’s still up to you to migrate your project itself, but Jetifier sorts third-party libraries for you by re-writing their binaries (Android Studio does also have a “Migrate to AndroidX” option, which takes some of the pain out of migration for you). It’s also worth pointing out that this happens in packaged artifacts, not in your source code. ![]() This step happens while compiling the app assuming that you have android.enableJetifier=true in your gradle.properties file.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |