flutter doctor reports that the Flutter plugin is not installed in Android Studio
Flutter plugin not installed; this adds Flutter specific functionality.Short answer
flutter doctor found Android Studio but not the Flutter plugin inside it. Open Settings, then Plugins, search the Marketplace for Flutter, install it, and restart the IDE. If the plugin will not install or load, check that you are on a stable Android Studio release, because the plugin does not support Canary builds.
Fix it fast
1Find out which cause you have
Run flutter doctor and read the Android Studio block: it shows which Android Studio it found and which plugin lines are missing.
flutter doctor2Match what you see, then jump to its fix
What does the error look like?
Flutter plugin not installed; this adds Flutter specific functionality.
Cause 1 of 2
The Flutter plugin was never installed, or the IDE was not restarted
1Check
Open the Plugins page of the IDE settings and look for Flutter under Installed.
# Android Studio on macOS: Android Studio > Settings > Plugins
# Windows / Linux: File > Settings > Plugins2Fix
In Plugins, open Marketplace, search for flutter, install the Flutter plugin, accept the prompts and restart when asked. Then run flutter doctor again.
# in the IDE: Plugins > Marketplace > "flutter" > Install > Restart
flutter doctor3Verify
The Android Studio block no longer shows the plugin warning.
flutter doctorConfirmed by docs.flutter.dev
Cause 2 of 2
The Android Studio build is not one the plugin supports
1Check
The plugin's README says the latest stable IntelliJ or Android Studio is supported, and that EAP versions are not always supported and Canary builds generally are not.
# Help > About Android Studio (macOS: Android Studio > About Android Studio)2Fix
Install the latest stable Android Studio, then install the Flutter plugin as in the first cause.
# Check for updates: macOS "Android Studio > Check for Updates", Linux "Help > Check for Updates"3Verify
Run flutter doctor again after restarting.
flutter doctorConfirmed by github.com
How do I stop it coming back?
- Update the Flutter and Dart plugins when the IDE offers it; updates ship regularly.
- Use a stable Android Studio release for Flutter work and keep Canary builds for other projects.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.
Which stack is behind this page?
Projects of mine built on the same technologies:
- TaxiDexMy own multi-tenant taxi dispatch SaaS: API, dispatcher portal, driver and passenger apps, and the servers underneath.
- QistLockA NestJS and React SaaS driving an Android Device Owner agent that locks financed phones when payments lapse.
- Dispatch ProA real-time logistics platform: Flutter apps, Spring Boot services and a Kafka event pipeline on AWS.
Related fixes
Mobile apps
Google Play says the app does not support 16 KB memory pages
check_elf_alignment.sh reports UNALIGNED for a library under lib/arm64-v8a
Google Play requires apps that target Android 15 or higher and ship native .so libraries to run on devices with 16 KB memory pages; from 1 February 2027 it will block updates that do not.
5 causes, each with a fixMobile apps
Gradle cannot find com.google.firebase:firebase-analytics-ktx
Required by: project :app
Firebase moved the Kotlin extensions into the main modules and stopped releasing the -ktx modules in July 2025.
2 causes, each with a fixMobile apps
Gradle cannot create LibraryVariantBuilderImpl in a Flutter Android build
Could not create an instance of type com.android.build.api.variant.impl.LibraryVariantBuilderImpl
This error appears when the Android Gradle plugin (AGP) cannot run in the Gradle or IDE you use.
3 causes, each with a fixMobile apps
Flutter release build cannot open the keystore: HmacPBESHA256 not available
Algorithm HmacPBESHA256 not available
The keystore is a PKCS12 file protected by a newer algorithm than the Java that is reading it understands.
3 causes, each with a fixMobile apps
Android install error: the package conflicts with an existing package of the same name
The package conflicts with an existing package by the same name
Android allows only one app per application ID, and an update must be signed with the same certificate as the installed version.
3 causes, each with a fixMobile apps
Android resource linking fails with resource android:attr/lStar not found
error: failed linking references.
The lStar attribute exists only from Android API 31.
2 causes, each with a fix