React Native安卓构建报AAPT2错误：资源缺失与版本适配问题

Hey there! As someone who’s stumbled through these frustrating Android build glitches before, let’s break down what’s going on and get your app up and running smoothly. Those missing resource errors (like android:style/TextAppearance.Material.Widget.Button.Borderless.Colored or android:attr/colorError) and AAPT2 issues almost always trace back to mismatched dependency versions or missing library references—super common for folks new to Android development with React Native.

Here’s a step-by-step guide to fix this:

1. Align Your Android SDK & Dependency Versions #

First, let’s make sure your project’s SDK versions and library dependencies are in sync:

• Open your project’s root android/build.gradle file:
  • Check the compileSdkVersion and targetSdkVersion—they should be set to a recent, stable version (like 33 or 34, depending on your React Native version). For example, React Native 0.70+ requires compileSdkVersion 33.
  • In the dependencies block, ensure the com.android.tools.build:gradle version matches your SDK version. For SDK 33, use gradle plugin version 7.4.2 or newer.
• Open android/app/build.gradle:
  • Add or verify you have the Material Components library included (this is where those missing Material-style resources live):

    implementation 'com.google.android.material:material:1.6.0'
    

    Match the material library version to your SDK—for SDK 33, 1.6.0 works perfectly.

2. Fix Your AndroidManifest.xml Theme #

Those missing Material resources often pop up if your app’s theme isn’t inheriting from a Material-compatible theme:

• In your AndroidManifest.xml, look for the android:theme attribute in the <application> tag. Replace it with a Material or AppCompat theme, like:

  android:theme="@style/Theme.MaterialComponents.Light.NoActionBar"
  

  Or if you prefer a React Native-specific theme, ensure it extends from AppCompat:

  android:theme="@style/Theme.AppCompat.Light.NoActionBar"
  

• Double-check for any typos in resource references in the Manifest (like misspelled style names or attributes)—even a tiny typo can trigger AAPT2 errors.

3. Clean Build Cache & Rebuild #

Cached build files are a frequent culprit for weird, unexplained errors:

• Open your terminal, navigate to the android folder of your project:

  cd android
  

• Run the clean command to wipe old build files:

  ./gradlew clean
  

• Go back to your project root and rebuild the app:

  cd ..
  react-native run-android
  

4. Verify React Native Version Compatibility #

Different React Native versions have strict requirements for Android SDK and dependency versions. If you’re on an older RN version, make sure your build.gradle settings match the official requirements for that release. For example:

• RN 0.68+ uses compileSdkVersion 31
• RN 0.70+ requires compileSdkVersion 33

If you’re still stuck after these steps, feel free to share snippets of your build.gradle and AndroidManifest.xml files (redact any sensitive info!) and we can dig deeper.

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