升级Gradle插件3.1.2后Butterknife无法使用问题求助

Hey there, I’ve run into exactly this issue when upgrading to Gradle Plugin 3.1.2 a while back, so let me walk you through what worked for me and share some thoughts on switching to Data Binding.

The main culprit here is usually a version mismatch between Butterknife and the new Gradle plugin. Here’s how to fix it step by step:

• Update Butterknife to a compatible version
  Gradle Plugin 3.1.x requires Butterknife 8.8.1 or higher—this was the first release that added support for the 3.1.x plugin family. Open your app-level build.gradle and update your dependencies to:

  implementation 'com.jakewharton:butterknife:8.8.1'
  annotationProcessor 'com.jakewharton:butterknife-compiler:8.8.1'
  

• Remove the android-apt plugin
  If you were using the old android-apt plugin for annotation processing, you need to ditch it entirely. Gradle Plugin 3.0+ has built-in support for annotation processors, so android-apt is no longer needed. Delete any lines like apply plugin: 'android-apt' from your app-level build.gradle, and remove the corresponding classpath entry from your project-level build.gradle.

• Clean up cached build files
  Old cached data often causes weird compatibility issues. Run Build > Clean Project followed by Build > Rebuild Project in Android Studio. If that doesn’t work, try invalidating caches via File > Invalidate Caches / Restart—this usually clears up stubborn build problems.

This depends on your project’s needs and your long-term goals, but here’s a balanced breakdown:

Reasons to make the switch #

• No more third-party compatibility headaches
  Data Binding is maintained by Google, so it’s guaranteed to work with future Android Studio/Gradle updates. You won’t have to deal with issues like this again down the line.
• More functionality than just view binding
  Unlike Butterknife, which only handles view injection and click listeners, Data Binding lets you bind data directly to layouts, handle complex UI logic in XML (with expressions), and integrate seamlessly with Jetpack components like ViewModel and LiveData. It reduces boilerplate across your entire codebase, not just view-related code.
• Future-proofing
  Data Binding is part of the official Jetpack ecosystem, so it’s here to stay. If you plan to adopt modern Android development practices, it’s a natural fit.

Potential downsides to consider #

• Steeper learning curve
  If you’re only used to Butterknife’s simple API, Data Binding has more concepts to learn—like layout wrapping, observable data objects, and expression syntax. It might take a few days to get comfortable with it.
• Initial setup overhead
  For an existing project, you’ll need to enable Data Binding in your build.gradle (add dataBinding { enabled = true } under the android block) and wrap all your layouts in the <layout> root tag. This can be tedious if you have a large number of layouts.
• Slightly longer build times
  Data Binding adds some processing time to your builds, though Google has optimized this significantly in newer Gradle versions. For most projects, this is a negligible trade-off.

Final call #

If you’re fed up with third-party library compatibility issues and want a more robust, feature-rich solution, switching to Data Binding is absolutely a smart move. It’ll pay off in the long run, especially if you’re planning to adopt Jetpack. But if your project is small and you just need a quick fix, updating Butterknife and cleaning your build should get you back up and running in no time.

内容的提问来源于stack exchange，提问作者alis