Android多模块项目编译报错：父类FlowViewModel无法解析

问题场景 #

开发简单多模块Android应用时，core:presentation模块中的open基类FlowViewModel，被feature:list:ui模块的ListScreenViewModel继承，项目使用Hilt做依赖注入。已确认feature:list:ui正确依赖core:presentation模块，但编译时仍出现父类无法解析的错误。

报错信息 #

Supertypes of the following classes cannot be resolved. Please make sure you have the required dependencies in the classpath:
class com.mvitemplate.feature.list.ui.ListScreenViewModel, unresolved supertypes: com.mvitemplate.core.presentation.mvi.FlowViewModel
Adding -Xextended-compiler-checks argument might provide additional information.

core:presentation 模块代码与配置 #

FlowViewModel 核心代码 #

import androidx.lifecycle.ViewModel
import kotlinx.coroutines.CoroutineScope
import kotlinx.coroutines.Dispatchers
import kotlinx.coroutines.SupervisorJob
import kotlinx.coroutines.cancel
import kotlinx.coroutines.launch

open class FlowViewModel<Intent, Result, ViewState> constructor(
    interactor: Interactor<Intent, Result>,
    private val reducer: Reducer<Result, ViewState>,
    initialState: ViewState,
    private val coroutineScope: CoroutineScope = CoroutineScope(SupervisorJob() + Dispatchers.Main.immediate)
): ViewModel(), BaseViewModel<Intent, ViewState> {

    override fun emit(intent: Intent) {
        coroutineScope.launch {
            // 业务逻辑代码
        }
    }

    override fun onCleared() {
        super.onCleared()
        coroutineScope.cancel()
    }
}

build.gradle.kts 配置 #

plugins {
    alias(libs.plugins.android.library)
    alias(libs.plugins.jetbrains.kotlin.android)
    alias(libs.plugins.dagger.hilt.android)
    alias(libs.plugins.google.devtools.ksp)
}

android {
    namespace = "com.mvitemplate.core"
    compileSdk = 34

    defaultConfig {
        minSdk = 24

        testInstrumentationRunner = "androidx.test.runner.AndroidJUnitRunner"
        consumerProguardFiles("consumer-rules.pro")
    }

    buildTypes {
        release {
            isMinifyEnabled = false
            proguardFiles(
                getDefaultProguardFile("proguard-android-optimize.txt"),
                "proguard-rules.pro"
            )
        }
    }
    compileOptions {
        sourceCompatibility = JavaVersion.VERSION_17
        targetCompatibility = JavaVersion.VERSION_17
    }
    kotlinOptions {
        jvmTarget = "17"
    }
}

dependencies {

    implementation(libs.androidx.core.ktx)
    implementation(libs.androidx.appcompat)
    implementation(libs.androidx.compose.runtime)
    implementation(libs.material)
    testImplementation(libs.junit)
    androidTestImplementation(libs.androidx.junit)
    androidTestImplementation(libs.androidx.espresso.core)

    implementation(libs.kotlinx.coroutines.android)
    implementation(libs.kotlinx.coroutines.core)

    // Hilt
    implementation(libs.hilt.android)
    ksp(libs.hilt.android.compiler)
}

feature:list:ui 模块代码与配置 #

ListScreenViewModel 代码 #

import com.mvitemplate.core.presentation.mvi.FlowViewModel
import com.mvitemplate.core.presentation.mvi.Interactor
import com.mvitemplate.core.presentation.mvi.Reducer
import com.mvitemplate.feature.list.ui.ListScreenContract.Intent
import com.mvitemplate.feature.list.ui.ListScreenContract.Result
import com.mvitemplate.feature.list.ui.ListScreenContract.ViewState
import dagger.hilt.android.lifecycle.HiltViewModel
import javax.inject.Inject

@HiltViewModel
class ListScreenViewModel @Inject constructor(
    interactor: Interactor<Intent, Result>,
    reducer: Reducer<Result, ViewState>,
    viewState: ViewState
): FlowViewModel<Intent, Result, ViewState>(
    interactor = interactor,
    reducer = reducer,
    initialState = viewState
)

build.gradle.kts 配置 #

plugins {
    alias(libs.plugins.android.library)
    alias(libs.plugins.jetbrains.kotlin.android)
    alias(libs.plugins.dagger.hilt.android)
    alias(libs.plugins.google.devtools.ksp)
}

android {
    namespace = "com.mvitemplate.feature.list.ui"
    compileSdk = 34

    defaultConfig {
        minSdk = 24

        testInstrumentationRunner = "androidx.test.runner.AndroidJUnitRunner"
        consumerProguardFiles("consumer-rules.pro")
    }

    buildTypes {
        release {
            isMinifyEnabled = false
            proguardFiles(
                getDefaultProguardFile("proguard-android-optimize.txt"),
                "proguard-rules.pro"
            )
        }
    }
    buildFeatures {
        compose = true
    }
    composeOptions {
        kotlinCompilerExtensionVersion = "1.5.1"
    }
    compileOptions {
        sourceCompatibility = JavaVersion.VERSION_17
        targetCompatibility = JavaVersion.VERSION_17
    }
    kotlinOptions {
        jvmTarget = "17"
        freeCompilerArgs += "-Xextended-compiler-checks"
    }
}

dependencies {

    implementation(project(":core:presentation"))

    implementation(libs.androidx.core.ktx)
    implementation(libs.androidx.appcompat)
    implementation(libs.androidx.activity.compose)
    implementation(platform(libs.androidx.compose.bom))
    implementation(libs.androidx.ui)
    implementation(libs.androidx.ui.graphics)
    implementation(libs.androidx.ui.tooling.preview)
    implementation(libs.androidx.material3)
    implementation(libs.material)
    testImplementation(libs.junit)
    androidTestImplementation(libs.androidx.junit)
    androidTestImplementation(libs.androidx.espresso.core)

    // Kotlin Coroutines
    implementation(libs.kotlinx.coroutines.android)
    implementation(libs.kotlinx.coroutines.core)

    // Navigation
    implementation(libs.androidx.navigation.compose)

    // Hilt
    implementation(libs.hilt.android)
    ksp(libs.hilt.android.compiler)
 }

排查与解决方案 #

1. 校验包名与导入路径 #

确认core:presentation模块中FlowViewModel文件的包声明，是否与ListScreenViewModel中的导入路径com.mvitemplate.core.presentation.mvi.FlowViewModel完全一致，排查拼写错误或目录结构不匹配问题。

2. 清理缓存并重建项目 #

执行以下操作：

1. 运行命令：./gradlew clean
2. 运行命令：./gradlew assembleDebug
3. 重启Android Studio，点击右上角Sync Project with Gradle Files按钮同步配置

3. 检查依赖传递性 #

如果FlowViewModel依赖的Interactor、Reducer、BaseViewModel等类型来自其他模块（如core:domain），core:presentation模块需要将这些依赖声明为api而非implementation，确保feature:list:ui能间接获取到这些类型：

// core:presentation的build.gradle.kts中修改依赖声明
api(project(":core:domain"))

4. 校验Hilt与KSP版本一致性 #

确认项目根目录libs.versions.toml中，Hilt版本与KSP版本匹配，避免版本冲突导致编译异常；同时确保两个模块都正确应用了Hilt和KSP插件，没有遗漏配置。

5. 检查Kotlin与Compose版本兼容性 #

feature:list:ui中kotlinCompilerExtensionVersion = "1.5.1"需与项目使用的Kotlin版本兼容（如Kotlin 1.9.x对应Compose Compiler 1.5.x），校验根目录libs.versions.toml中的版本匹配性。

内容的提问来源于Stack Exchange，提问作者Daniel Iroka