Resolving Resource Not Found Errors in values.xml with Android AppCompat v7 r21

Problem Background and Error Analysis

During Android development, many developers encounter severe compilation errors when integrating AppCompat v7 library version 21.0.0. These errors primarily manifest as unavailable resource attributes in values.xml files, specifically including “android:actionModeShareDrawable”, the “android:TextAppearance.Material” series attributes, and Material Design-related color attributes.

The error messages appear in multiple values directories including values-v11, values-v14, and values-v21. The core issue stems from AppCompat v21 library's dependency on new APIs and resource attributes introduced in Android 5.0 (API level 21). When the project's compilation target version is lower than API 21, the system cannot recognize these new resource references, resulting in compilation failures.

Root Cause Investigation

The primary purpose of AppCompat v7 library is to provide backward compatibility support for new version UI components on older Android systems. However, starting from version 21, AppCompat library deeply integrates Material Design language, which requires the development environment to have access to new resource attributes introduced in Android 5.0 and later versions.

Specifically, Material Design-related text appearance attributes (such as “TextAppearance.Material”), theme overlay attributes (like “ThemeOverlay.Material”), and color attributes (including “colorPrimary”, “colorAccent”, etc.) were first introduced in API 21. If the project's compileSdkVersion is set lower than 21, the Android build system cannot resolve these attribute references.

Solution Implementation

To resolve this issue, ensure the project's compilation configuration correctly points to API 21 or higher. Here are the specific configuration steps:

First, open the build.gradle file in your project (typically the build.gradle in the app module). In the android configuration block, set the correct compileSdkVersion and buildToolsVersion:

android {
    compileSdkVersion 21
    buildToolsVersion "21.0.1"
    
    defaultConfig {
        applicationId "com.example.yourapp"
        minSdkVersion 14
        targetSdkVersion 21
        versionCode 1
        versionName "1.0"
    }
}

In this configuration, compileSdkVersion 21 specifies the Android API level used during project compilation, ensuring the build system can recognize all resource attributes introduced in API 21. buildToolsVersion "21.0.1" specifies the build tools version, recommending using the latest stable version available at the time.

It's important to note that minSdkVersion can remain at a lower value (such as 14), which doesn't affect the compilation process but determines the minimum Android version the application can run on. targetSdkVersion should typically match compileSdkVersion to ensure optimal application performance on newer system versions.

Configuration Verification and Best Practices

After modifying Gradle configuration, recommended verification steps include:

1. Sync Gradle Project: In Android Studio, click the “Sync Project with Gradle Files” button to ensure all configuration changes are properly applied.

2. Clean Project: Execute “Build > Clean Project” operation to clear previous build cache and intermediate files.

3. Rebuild Project: Execute “Build > Rebuild Project” to verify all compilation errors are resolved.

As best practices, developers should:

- Regularly update Android SDK and build tools to the latest stable versions

- Check and update compileSdkVersion when upgrading support library versions

- Use Android Studio's auto-import feature to ensure all dependency version compatibility

- Standardize SDK and build tool versions across all developers in team environments

Deep Understanding of Build Process

To better understand the nature of this issue, it's essential to comprehend how the Android build system works. When adding AppCompat dependency, Gradle downloads the corresponding AAR (Android Archive) files and extracts them to the intermediates/exploded-aar directory during the build process.

These AAR files contain resource files targeting different API levels. AppCompat v21's AAR includes the values-v21 directory, which defines resources dependent on new features in API 21. During resource merging, the build system determines how to handle these version-specific resources based on the project's compileSdkVersion.

If compileSdkVersion is lower than 21, the build system cannot correctly resolve resource references in the values-v21 directory because the corresponding attribute definitions don't exist in lower version Android frameworks. This explains why “No resource found” errors occur.

By correctly setting compileSdkVersion, the build system gains access to the complete API 21 framework definitions, successfully resolving all Material Design-related resource attributes and ensuring the project compiles smoothly.