一、简述

最近升级到 Flutter 3.x 及以上版本的朋友，想必在编译项目时都被控制台这行显眼的警告刷过屏：

这条警告让人心里发寒：万恶的 KGP要被“抛弃”了！

从 Android Gradle Plugin 开始，对 Kotlin 的支持已被彻底收归“内置”。任何插件中单方面显式声明 apply plugin: 'kotlin-android'在未来的 Flutter 编译环境中都会直接导致建立崩溃。

官方指引给出的路线非常直接：只要把插件最低 Flutter 版本限制升到一个更高版本，接下来删掉 apply plugin: 'kotlin-android'收工！

但在实际开源组件维护中，如果我们强行把最低版本拔高到最新 Flutter。就相当于与那些还在使用旧版 Flutter的使用者们“割袍断义”了！本篇教程将为你提供新旧 Flutter 双向兼容的适配方法帮助你在不破坏现有使用者体验的前提下顺利迁移。

二、新旧版本对比

先用一张表直观对比新旧两种编译环境下机制差异。让你知己知彼，“针对这个问题”。

三、动态兼容方案

动态应用 kotlin-android 插件

Solve problem of static RegExp detection by flutter_tools that simply scans for any literal occurrence of `apply plugin:"kotlin-android"` or `id "org.jetbrains.kotlin.android"` in your build.gradle file.

// 获取当前编译环境中 Android Gradle 插件的主版本号
def agpMajor = com.android.Version.ANDROID_GRADLE_PLUGIN_VERSION.tokenize as int
// 判断当前内置 Kotlin 是否生效
def builtInKotlinActive = agpMajor>= 7 && ||
Boolean.parseBoolean.toString))
// 在内置 Kotlin 不生效时才手动 apply
if {
apply plugin: "kotlin-" + "android"
}

• The first line extracts AGP major version . If you see a compile error “Cannot find symbol ANDROID_GRADLE_PLUGIN_VERSION”,you’re on an older AGP – no worries.
• The second line checks if Built‑in Kotlin is active;it also respects a project property `android.builtInKotlin` which can be set to false when you intentionally disable it.
• If Built‑in is not active,we dynamically generate plugin name and call `apply`. This avoids static literal detection while still providing necessary support.

A: Why not just write `apply plugin:"kotlin-android"`?

This would trigger flutter_tools regex scanner immediately regardless of any surrounding logic,leading to warnings or even build failures on newer versions where Built‑in Kotlin already exists.

动态配置 JVM target

Kotlin 的 DSL 在不同 KGP 版本之间存在差异。下面的代码会根据当前环境自动选择合适语法，从而避免因写错属性导致编译报错。

// 获取 project 中 kotlin
对象
def kotlinExt = project.extensions.findByName
if ) {
// Newer DSL
kotlin {
compilerOptions {
jvmTarget = org.jetbrains.kotlin.gradle.dsl.JvmTarget.JVM_1_8
}
}
} else {
// Legacy DSL
android.kotlinOptions {
jvmTarget = JavaVersion.VERSION_1_8.toString
}
}

• The first line safely fetches Kotlin extension object;话说回来，if it’s missing we skip configuration altoger.
• If `compilerOptions` exists,we are on a modern environment – use `compilerOptions` block.
• If not,fall back to classic `android.kotlinOptions` syntax so older projects don’t crash with “unknown property” errors.

四、最终一句话——平滑兼容实际经验

• You can now ship a single Gradle file that works across both old and new builds without forcing users to upgrade ir entire Flutter SDK stack.
• No need to add y flags like `android.builtInKotlin=false ` in gradle.properties – let your plugin decide automatically.
• The only trade‑off is slightly more verbose build.gradle code。but this cost is negligible compared to preventing fatal build failures or losing users due to incompatibility.

P.S. 如果你正在维护一个多网站项目并担心类似 KGP 冲突，请先检查项目中是否还有硬编码 `apply plugin:'kotlin-android'` 或 `id 'org.jetbrains.kotlin.android'`。及时调整可以避免未来发布时踩坑。祝编码愉快，下期见，

If this article helps you out,please consider following my WeChat public account FSA Full Stack Action!Your support means everything – plus I’ll share more Android,iOS & Python insights you might find useful!