Android项目AutoValue代码未生成，报错找不到AutoValueGson相关类

Hey there, let's work through this AutoValue code generation issue together—missing generated classes like AutoValue_AutoValueGsonFactory are a common headache, but we can fix it step by step.

1. Double-Check Your Gradle Dependencies #

First, make sure you've added all required dependencies correctly, and that you're using the right configuration for your Android Gradle Plugin version (3.0+ uses annotationProcessor instead of the old apt plugin):

dependencies {
    // AutoValue core annotations (for your model classes)
    implementation 'com.google.auto.value:auto-value-annotations:1.10.1'
    // AutoValue processor (handles code generation)
    annotationProcessor 'com.google.auto.value:auto-value:1.10.1'
    
    // AutoValue-Gson extension annotations
    implementation 'com.ryanharter.auto.value:auto-value-gson:1.1.1'
    // AutoValue-Gson processor
    annotationProcessor 'com.ryanharter.auto.value:auto-value-gson:1.1.1'
}

Note: Use the latest compatible versions for these libraries—version mismatches often cause generation failures.

If you're using Kotlin in your project, replace annotationProcessor with kapt and make sure you've applied the kotlin-kapt plugin at the top of your app/build.gradle:

apply plugin: 'com.android.application'
apply plugin: 'kotlin-android'
apply plugin: 'kotlin-kapt' // Add this line

// ... rest of your gradle config ...

dependencies {
    // ... other dependencies ...
    kapt 'com.google.auto.value:auto-value:1.10.1'
    kapt 'com.ryanharter.auto.value:auto-value-gson:1.1.1'
}

2. Verify Your AutoValueGsonFactory Implementation #

Your factory class needs to follow the exact pattern required by AutoValue-Gson—if it's misannotated or structured wrong, code won't generate. Here's the correct template:

import com.google.gson.TypeAdapterFactory;
import com.ryanharter.auto.value.gson.GsonTypeAdapterFactory;

@GsonTypeAdapterFactory // Don't miss this annotation!
public abstract class AutoValueGsonFactory implements TypeAdapterFactory {

    // Static method to return the generated implementation
    public static TypeAdapterFactory create() {
        return new AutoValue_AutoValueGsonFactory(); // This is the generated class Android can't find
    }
}

Key checks:

• The class is abstract and implements TypeAdapterFactory
• It has the @GsonTypeAdapterFactory annotation (from the AutoValue-Gson library)
• The static create() method references the generated class with the AutoValue_ prefix (match your factory class name exactly)

3. Confirm Annotation Processor Settings in Android Studio #

Even if you've checked "Enable annotation processing", double-check these details:

• Go to File > Settings > Build, Execution, Deployment > Compiler > Annotation Processors
• Ensure "Enable annotation processing" is checked
• Under "Store generated sources in", select "Module content root" (the path should be build/generated/source/apt/debug or release for your module)
• Make sure Android Studio recognizes this generated directory: if it's not highlighted as a source folder, right-click it > Mark Directory as > Generated Sources Root

4. Clean, Sync, and Rebuild (The Classic Fix) #

Android Studio's cache can sometimes get stuck, so let's reset things:

1. Go to File > Invalidate Caches... > Invalidate and Restart (this clears stale cache files)
2. Once Studio restarts, go to File > Sync Project with Gradle Files
3. Finally, run Build > Rebuild Project (avoid "Make Project"—Rebuild ensures full code generation)

5. Add Annotation Processor Classpath Configuration #

For some Android Gradle Plugin versions, you need to explicitly allow the processor to access the compile classpath. Add this to your android block in app/build.gradle:

android {
    defaultConfig {
        // ... your existing config ...
        javaCompileOptions {
            annotationProcessorOptions {
                includeCompileClasspath true
            }
        }
    }
}

If you've gone through all these steps, your AutoValue classes should generate properly, and the "cannot find symbol" error should disappear.

内容的提问来源于stack exchange，提问作者Kevin Ramirez Zavalza