Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages
Flutter and app store releases

Flutter build fails because the Android project uses the v1 embedding

ErrorBuild failed due to use of deprecated Android v1 embedding

Short answer

Your Android project was made before Flutter 1.12 and still uses the v1 embedding, while the plugins you use need v2. Add the flutterEmbedding meta-data with value 2 to AndroidManifest.xml, make MainActivity extend the v2 FlutterActivity, and drop the old FlutterApplication class. Then rebuild.

  • Applies to Flutter 3.x, Android Gradle Plugin 8.x
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Fix it fast

  1. 1Find out which cause you have

    Look for the v1 signs in the Android project: the old application class and an activity that imports io.flutter.app.

    grep -rn "io.flutter.app\|flutterEmbedding\|GeneratedPluginRegistrant" android/app/src/main
  2. 2Match what you see, then jump to its fix

    1. 1No flutterEmbedding entry, or android:name="io.flutter.app.FlutterApplication" on the application tagThe manifest does not declare the v2 embeddingFix
    2. 2MainActivity imports io.flutter.app.FlutterActivity or calls GeneratedPluginRegistrant.registerWith(this) in onCreateMainActivity extends the old FlutterActivity or registers plugins by handFix
    3. 3Calls to FlutterMain.startInitialization, or imports from io.flutter.facadeAn add-to-app module still uses FlutterMain or the facade packageFix

What does the error look like?

  • Build failed due to use of deprecated Android v1 embedding

Cause 1 of 3

The manifest does not declare the v2 embedding

1Check

Open the manifest and look inside the application element.

cat android/app/src/main/AndroidManifest.xml

2Fix

Replace the old application name with the placeholder and add the embedding flag inside application.

<application
    android:name="${applicationName}">
    <meta-data
        android:name="flutterEmbedding"
        android:value="2" />
</application>

3Verify

Build the app.

flutter build apk --debug

Confirmed by github.com

Did this fix it?

Cause 2 of 3

MainActivity extends the old FlutterActivity or registers plugins by hand

1Check

Print MainActivity and read its imports and onCreate.

cat android/app/src/main/*/*/*/MainActivity.* 2>/dev/null || find android/app/src/main -name 'MainActivity.*'

2Fix

Extend the v2 FlutterActivity and delete the onCreate override. FlutterActivity registers plugins itself when the engine is created. If you add custom platform channels, set them up in configureFlutterEngine and call GeneratedPluginRegistrant.registerWith(flutterEngine) there.

// MainActivity.kt
import io.flutter.embedding.android.FlutterActivity

class MainActivity : FlutterActivity()

3Verify

Run the app on a device or emulator.

flutter run

Confirmed by github.com

Did this fix it?

Cause 3 of 3

An add-to-app module still uses FlutterMain or the facade package

1Check

Search the host Android app that embeds Flutter.

grep -rn "FlutterMain\|io.flutter.facade" android/ .

2Fix

Remove the FlutterMain initialisation calls, since Flutter initialises itself. Use io.flutter.embedding.android.FlutterFragment in place of io.flutter.facade.FlutterFragment, or FlutterView from the embedding package when you need a view.

// replace io.flutter.facade.FlutterFragment with
import io.flutter.embedding.android.FlutterFragment

3Verify

Rebuild the host app.

./gradlew assembleDebug

Confirmed by github.com

Did this fix it?

How do I stop it coming back?

  • Do not hand-edit generated files such as GeneratedPluginRegistrant; call it only from configureFlutterEngine when you must.
  • Compare your android folder with a fresh flutter create project when you upgrade Flutter by several versions.
  • Let FlutterActivity register plugins instead of doing it in onCreate.

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:

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 fix

Next step

Want this handled for good?

I look after servers, apps and releases end to end. Tell me what keeps breaking.