Short answer
Raise the Kotlin version in your Android build files. In projects made with Flutter 3.16 or later it is the org.jetbrains.kotlin.android line in android/settings.gradle (or settings.gradle.kts). In older projects it is ext.kotlin_version in android/build.gradle, which is the file Flutter’s error message names even on newer projects. To find a version that works with your Flutter release, create a new project with the same Flutter version and copy its value, then run flutter clean and build again.
Where the Kotlin version lives, and how to raise it
01
Projects made with Flutter 3.16 or later: settings.gradle
“For example, the Kotlin version is now configured in the android/settings.gradle file.” Flutter, Required Kotlin version
Newer projects declare their plugins in android/settings.gradle, and the Kotlin version is on the org.jetbrains.kotlin.android line. Raise that number. Replace {kotlinVersion} and {agpVersion} below with real version numbers; don’t paste the braces. Current Flutter creates settings.gradle.kts, where the same line uses Kotlin syntax.
plugins { id "dev.flutter.flutter-plugin-loader" version "1.0.0" id "com.android.application" version "{agpVersion}" apply false id "org.jetbrains.kotlin.android" version "{kotlinVersion}" apply false } // settings.gradle.kts plugins { id("org.jetbrains.kotlin.android") version "{kotlinVersion}" apply false }02
Older projects: ext.kotlin_version in android/build.gradle
“If you have generated your project with an older version of Flutter, it's advisable to upgrade your build scripts to the newest form.” Flutter, Required Kotlin version
Projects created before that keep the version in the buildscript block of android/build.gradle, as ext.kotlin_version. Raising it fixes the error, but Flutter recommends moving these files to the new declarative format, which is a one-time change worth doing before the next upgrade.
buildscript { ext.kotlin_version = '{kotlinVersion}' }03
Pick the version from a fresh project, not from a forum post
Versions that work depend on your Flutter release and your Android Gradle Plugin version. The safest source is a new project made by the same Flutter you use: run flutter create in a scratch folder and copy the Kotlin and Android Gradle Plugin versions from its android/settings.gradle. Change both together if the new project’s Android Gradle Plugin is newer too.
flutter --version flutter create /tmp/kotlin_check grep -n "kotlin\|com.android.application" /tmp/kotlin_check/android/settings.gradle*04
“Incompatible version of Kotlin”: a plugin was built with a newer one
The metadata message names two versions: the one a library was compiled with and the one your project expects. Raise your project’s Kotlin version to at least the first number, using the steps above. Then run flutter clean, flutter pub get and build again, so no stale Gradle output is reused.
Checked against the vendor’s docs on : Flutter docs: Required Kotlin version; Flutter docs: Deprecated imperative apply of Flutter’s Gradle plugins.
Rather hand it over?
Fixed scope, fixed price, paid upfront. The work happens in writing; no call needed.
- from $450App Fix TicketOne reproducible bug in an existing mobile or web app, diagnosed and fixed.See scope and start
- from $450AI-Built App RescueA Lovable, Bolt or Cursor app checked end to end in 3 days, then its worst problems fixed at a fixed price.No issues worth fixing, no charge. If the Launch Check finds nothing rated medium or higher, Simon refunds the full $450. You keep the report either way. This applies to the first 10 Launch Checks bought after October 30, 2026.See scope and start
Related: Flutter “Gradle task assembleDebug failed” · Flutter “Unsupported class file major version” · Google Play target API level 35 and 36 · Flutter MissingPluginException