向类传递Context变量时Android应用崩溃求助

看起来你在使用Jetpack Compose搭配Room数据库时，调用Queries类导致应用崩溃了，我来帮你一步步排查问题所在：

首先先整理下你提供的项目配置，方便分析：

1. 版本目录（libs.versions.toml） #

[versions]
agp = "8.10.1"
kotlin = "2.0.21"
coreKtx = "1.16.0"
junit = "4.13.2"
junitVersion = "1.2.1"
espressoCore = "3.6.1"
lifecycleRuntimeKtx = "2.9.0"
activityCompose = "1.10.1"
composeBom = "2024.09.00"
roomCommonJvm = "2.7.1"
roomRuntimeAndroid = "2.7.1"
material3WindowSizeClassAndroid = "1.3.2"
benchmarkMacro = "1.3.4"
composeMaterial3 = "1.5.0-beta03"

[libraries]
androidx-core-ktx = { group = "androidx.core", name = "core-ktx", version.ref = "coreKtx" }
junit = { group = "junit", name = "junit", version.ref = "junit" }
androidx-junit = { group = "androidx.test.ext", name = "junit", version.ref = "junitVersion" }
androidx-espresso-core = { group = "androidx.test.espresso", name = "espresso-core", version.ref = "espressoCore" }
androidx-lifecycle-runtime-ktx = { group = "androidx.lifecycle", name = "lifecycle-runtime-ktx", version.ref = "lifecycleRuntimeKtx" }
androidx-activity-compose = { group = "androidx.activity", name = "activity-compose", version.ref = "activityCompose" }
androidx-compose-bom = { group = "androidx.compose", name = "compose-bom", version.ref = "composeBom" }
androidx-ui = { group = "androidx.compose.ui", name = "ui" }
androidx-ui-graphics = { group = "androidx.compose.ui", name = "ui-graphics" }
androidx-ui-tooling = { group = "androidx.compose.ui", name = "ui-tooling" }
androidx-ui-tooling-preview = { group = "androidx.compose.ui", name = "ui-tooling-preview" }
androidx-ui-test-manifest = { group = "androidx.compose.ui", name = "ui-test-manifest" }
androidx-ui-test-junit4 = { group = "androidx.compose.ui", name = "ui-test-junit4" }
androidx-material3 = { group = "androidx.compose.material3", name = "material3" }
androidx-room-common-jvm = { group = "androidx.room", name = "room-common-jvm", version.ref = "roomCommonJvm" }
androidx-room-runtime-android = { group = "androidx.room", name = "room-runtime-android", version.ref = "roomRuntimeAndroid" }
androidx-material3-window-size-class1-android = { group = "androidx.compose.material3", name = "material3-window-size-class-android", version.ref = "material3WindowSizeClassAndroid" }
androidx-benchmark-macro = { group = "androidx.benchmark", name = "benchmark-macro", version.ref = "benchmarkMacro" }
androidx-compose-material3 = { group = "androidx.wear.compose", name = "compose-material3", version.ref = "composeMaterial3" }

[plugins]
android-application = { id = "com.android.application", version.ref = "agp" }
kotlin-android = { id = "org.jetbrains.kotlin.android", version.ref = "kotlin" }
kotlin-compose = { id = "org.jetbrains.kotlin.plugin.compose", version.ref = "kotlin" }

2. 模块build.gradle（部分） #

plugins {
    alias(libs.plugins.android.application)
    alias(libs.plugins.kotlin.android)
    alias(libs.plugins.kotlin.compose)
}

android {
    namespace = "com.example.testinganddebugging"
    compileSdk = 35

    defaultConfig {
        applicationId = "com.example.testinganddebugging"
        minSdk = 24
        targetSdk = 35
        versionCode = 1
        versionName = "1.0"

        testInstrumentationRunner = "androidx.test.runner.AndroidJUnitRunner"
    }

    buildTypes {
        release {
            isMinifyEnabled = false
            proguardFiles(
                getDefaultProguardFile("proguard-android-optimize.txt"),
                "proguard-rules.pro"
            )
        }
    }

    compileOptions {
        sourceCompatibility = JavaVersion.VERSION_11
        targetCompatibility = JavaVersion.VERSION_11
    }

    kotlinOptions {
        jvmTarget = "11"
    }

    buildFeatures {
        compose = true
    }
}

val room_version = "2.7.2"

dependencies {
    implementation(libs.androidx.core.ktx)
    implementation(libs.androidx.lifecycle.runtime.ktx)
    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.androidx.room.common.jvm)
    implementation(libs.androidx.room.runtime.android)
    implementation("androidx.room:room-runtime:$room_version") // 重复依赖且版本不一致

    testImplementation(libs.junit)
    androidTestImplementation(libs.androidx.junit)
    androidTestImplementation(libs.androidx.espresso.core)
    // 此处内容被截断，假设后续还有其他依赖
}

可能的崩溃原因及修复方案 #

1. Room依赖版本冲突+缺少必要组件

你目前的Room依赖存在两个明显问题：

• 重复引入且版本不一致：既通过libs.androidx.room.runtime.android引入了2.7.1版本，又手动添加了2.7.2版本的room-runtime，版本不匹配会导致类加载冲突，直接引发崩溃。
• 缺少注解处理器：Room需要通过注解处理器自动生成DAO和Database的实现类，没有这部分依赖的话，运行时会找不到核心类，导致崩溃。

修复步骤：

• 移除手动添加的implementation("androidx.room:room-runtime:$room_version")，统一使用libs目录中定义的2.7.1版本。
• 添加Room注解处理器依赖，同时启用kapt插件（Kotlin项目必备）：
  先在plugins块中添加kapt插件：

  plugins {
      // 保留已有的插件...
      id("org.jetbrains.kotlin.kapt") version libs.versions.kotlin.get()
  }
  

  然后在dependencies中添加注解处理器：

  kapt("androidx.room:room-compiler:2.7.1") // 版本必须和runtime保持一致
  

2. 在Composable中直接操作数据库/传递Context的问题

Composable函数的生命周期跟随UI状态频繁变化，直接在里面初始化Queries类（尤其是需要Context的类）很容易踩坑：

• 传递Activity Context会导致内存泄漏，进而引发崩溃。
• 数据库实例未正确初始化，出现空指针异常。
• Composable重组时重复创建实例，引发资源冲突。

修复步骤：

• 用ViewModel封装数据库操作逻辑：ViewModel持有Application Context，生命周期稳定，不会随UI重组销毁。示例代码：

  class MainViewModel(application: Application) : AndroidViewModel(application) {
      // 初始化Room数据库实例
      private val db = Room.databaseBuilder(
          application,
          YourDatabaseClass::class.java, "your-db-name"
      ).build()
      // 获取Queries/DAO实例
      val queries = db.yourQueries()
  
      // 封装数据库操作方法，供Composable调用
      fun fetchData() = viewModelScope.launch {
          // 调用queries的查询方法
      }
  }
  

• 在Composable中通过viewModel()获取实例，间接调用数据库操作：

  @Composable
  fun TestScreen() {
      val viewModel: MainViewModel = viewModel()
      // 在协程中执行数据库操作，避免阻塞主线程
      LaunchedEffect(Unit) {
          viewModel.fetchData()
      }
  }
  

• 如果Queries类必须接收Context，务必传递Application Context（通过applicationContext获取），避免使用Activity Context。

3. 查看崩溃日志精准定位

如果以上修复后仍崩溃，建议打开Android Studio的Logcat，找到崩溃的具体异常信息（比如NullPointerException、ClassNotFoundException或Cannot access database on main thread），这能帮你更快锁定问题。比如遇到主线程数据库操作的问题，要么在Room构建时临时允许主线程查询（仅测试用），要么严格在协程中执行查询。

内容来源于stack exchange