Hey there! Let's work through those errors you're hitting after importing the EventShare_AndroidApp project. Both issues tie back to Android resource processing, so let's break down fixes for each one:

1. Resolving "invalid resource type 'attr' for parent of style" #

This error almost always happens when you're trying to inherit a style from an attribute incorrectly, or there's a version mismatch in your support libraries. Here's how to fix it:

• Check style inheritance syntax in styles.xml:
  Look for any style declarations where the parent is set to @attr/[attribute-name] instead of ?attr/[attribute-name]. For example, if you see:

  <style name="CustomToolbarStyle" parent="@attr/toolbarStyle">
  

  Change it to:

  <style name="CustomToolbarStyle" parent="?attr/toolbarStyle">
  

  The ? syntax tells Android to reference the attribute value from the current theme, which is the correct way to inherit styles defined as attributes.

• Align support library/AndroidX versions:
  Open your module-level build.gradle file and make sure all your AppCompat or AndroidX dependencies are using the same stable version. For example, if using AndroidX, update to a recent version like:

  implementation 'androidx.appcompat:appcompat:1.6.1'
  implementation 'androidx.constraintlayout:constraintlayout:2.1.4'
  

  Mismatched versions often cause resource conflicts that trigger this error.

• Clean and rebuild your project:
  Corrupted build cache can sometimes cause false resource errors. In Android Studio, go to Build > Clean Project, then Build > Rebuild Project. You can also run this command in the terminal:

  ./gradlew clean assembleDebug
  

2. Fixing "aapt2 error: check logs for details" #

This error is usually a side effect of the first issue—AAPT2 (Android Asset Packaging Tool 2) fails to process resources because of the style inheritance problem. Once you fix the first error, this one often disappears. If it doesn't, do this:

• View full AAPT2 error logs:
  In Android Studio, open the Build tool window (View > Tool Windows > Build), switch to the Build Output tab, and scroll through the logs. You'll find specific details like which resource file (e.g., res/values/styles.xml) and line number is causing the problem. This is critical for pinpointing hidden issues like unclosed XML tags or invalid attribute values.

• Validate resource file syntax:
  Check for common XML mistakes in your resource files:

  • Unclosed tags (e.g., <TextView> without </TextView>)
  • Invalid color formats (missing # at the start, like FFFFFF instead of #FFFFFF)
  • Misspelled attribute names (e.g., android:textColo instead of android:textColor)
  • Resource filenames with uppercase letters or special characters (Android requires resource filenames to be lowercase with underscores only)

• Temporary workaround (not recommended long-term):
  If you need to get the project running quickly while debugging, you can disable AAPT2 by adding this line to your gradle.properties file:

  android.enableAapt2=false
  

  Note that this uses the older AAPT tool, which is deprecated, so only use this as a short-term fix while you find the root cause.

Extra Troubleshooting Steps #

• Match the project's SDK versions:
  Verify that your local Android SDK has the minSdkVersion, targetSdkVersion, and compileSdkVersion specified in the project's build.gradle installed. Mismatched SDK versions can lead to unexpected resource processing errors.
• Check for missing resources:
  Ensure all resources referenced in the project (like drawables, strings, or themes) are present in your local copy. Sometimes imported projects might have missing files if they were excluded from the GitHub repo.

Once you work through these steps, the project should build successfully!

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