AI & TechnologyFlutter "Applying Gradle Plugin Imperatively" Error: The Fix

If an Android build fails with "You are applying Flutter's main Gradle plugin imperatively using the apply script method, which is not possible anymore", your Gradle files still load Flutter the pre-3.16 way. Flutter 3.29 removed support for that method, so the old flutter.gradle file now does nothing but throw this error. The fix is to move three Gradle files to the declarative plugins {} block. It changes how the build is wired, not your app's code.

If you landed here from the link in the error message, flutter.dev/to/flutter-gradle-plugin-apply, it still opens Flutter's migration page. This guide follows that page and adds what the page doesn't say: when the old method stopped working, and the Firebase case most older apps have. The facts come from Flutter's docs, its source code and its release archive, as listed in the sources. I checked each one on October 18, 2026.

Disclosure: App369 is my studio. I build and fix Flutter apps, and the last section mentions what I sell. Google doesn't pay me for anything on this page.

What changed, and when

Flutter's docs page lists only when the new method was supported and recommended. The removal date comes from the pull request. I checked that its commit is in the 3.29.0 tag and not in 3.27.

The two versions of the error

Both come from files in Flutter's own Gradle folder that now exist only to throw an error:

• flutter.gradle: "You are applying Flutter's main Gradle plugin imperatively using the apply script method, which is not possible anymore." This means android/app/build.gradle still has apply from: ".../flutter.gradle".
• app_plugin_loader.gradle: "You are applying Flutter's app_plugin_loader Gradle plugin imperatively using the apply script method, which is not possible anymore." This means android/settings.gradle still loads the plugin loader the old way.

Both point to the same migration page, and the fix below covers both.

The fix, file by file

These steps follow Flutter's migration page. My advice: commit or back up the android folder before you start, so you can compare.

1. Note your AGP and Kotlin versions

Open android/build.gradle. In the buildscript block, the Android Gradle Plugin version is the number at the end of classpath 'com.android.tools.build:gradle:...', and the Kotlin version is in ext.kotlin_version = '...'. You need both in the next step.

2. Replace android/settings.gradle

Flutter's page gives this as the new contents. Replace {agpVersion} and {kotlinVersion} with the versions from step 1:

pluginManagement {
    def flutterSdkPath = {
        def properties = new Properties()
        file("local.properties").withInputStream { properties.load(it) }
        def flutterSdkPath = properties.getProperty("flutter.sdk")
        assert flutterSdkPath != null, "flutter.sdk not set in local.properties"
        return flutterSdkPath
    }()

    includeBuild("$flutterSdkPath/packages/flutter_tools/gradle")

    repositories {
        google()
        mavenCentral()
        gradlePluginPortal()
    }
}

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
}

include ":app"

If you had your own code in this file, keep it after the pluginManagement {} and plugins {} blocks. Gradle doesn't allow other code before them. The plugin loader must not be set to apply false.

3. Remove buildscript from android/build.gradle

Delete the whole buildscript { ... } block. The allprojects, subprojects and clean parts stay.

4. Update android/app/build.gradle

Remove the def flutterRoot = localProperties.getProperty('flutter.sdk') line and the if (flutterRoot == null) { throw ... } block that follows it. Keep the code that loads local.properties, which the version settings still use. Then remove the old apply lines. In Flutter 3.10's flutter create template they look like this:

apply plugin: 'com.android.application'
apply plugin: 'kotlin-android'
apply from: "$flutterRoot/packages/flutter_tools/gradle/flutter.gradle"

Then add this at the very top of the file:

plugins {
    id "com.android.application"
    id "kotlin-android"
    id "dev.flutter.flutter-gradle-plugin"
}

Flutter's page points out that dev.flutter.flutter-gradle-plugin here is a different ID from dev.flutter.flutter-plugin-loader in settings.gradle. If the dependencies block has org.jetbrains.kotlin:kotlin-stdlib-jdk7:$kotlin_version, remove that line.

5. Build and run

Flutter's page says to run flutter run and check that the app builds and launches on an Android device or emulator.

If the app uses Firebase

If your app uses Firebase, its Google Services plugin, and Crashlytics if you use it, are probably applied the old way too. Flutter's page covers this case:

1. In android/build.gradle, remove the classpath lines for com.google.gms:google-services and com.google.firebase:firebase-crashlytics-gradle. Note their versions first.
2. In android/app/build.gradle, remove apply plugin: 'com.google.gms.google-services' and apply plugin: 'com.google.firebase.crashlytics'.
3. Add both to the plugins block in android/settings.gradle, with the versions you noted and apply false:

   id "com.google.gms.google-services" version "4.4.0" apply false
   id "com.google.firebase.crashlytics" version "2.9.9" apply false
   

4. Add id "com.google.gms.google-services" and id "com.google.firebase.crashlytics" to the plugins block in android/app/build.gradle, without versions.

The versions above are the ones in Flutter's example. Use the versions your project had, or newer ones.

If the build still fails after this

In my view, a project old enough to hit this error usually has more than one problem waiting: old plugins, an old AGP or Gradle version, or the v1 embedding. If the next error says "Build failed due to use of deleted Android v1 embedding", see the v1 embedding fix, also removed in Flutter 3.29. If Gradle can't find jcenter(), see the JCenter guide.

Need a hand?

If an older Flutter app won't build after an upgrade, the App Fix Ticket covers it in two fixed-price steps. A $450 Diagnosis gives you the root cause with evidence and a fixed repair quote within 3 business days, credited toward the fix. If you go ahead, the $1,200 Fix takes 5 business days and comes as a pull request. Or send me a short description.