Flutter 3.44.0 – Android release AAB build fails at the very end on Windows and macOS
Summary
Since upgrading to Flutter 3.44.0 (stable), Android release bundle builds fail consistently on both Windows and macOS.
The Gradle bundleRelease task runs for several minutes and appears to complete, but Flutter fails during the final post-build step with:
Running Gradle task 'bundleRelease'... 441,4s
Release app bundle failed to strip debug symbols from native libraries.
Please run flutter doctor and ensure that the Android toolchain does not
report any issues.
Otherwise, file an issue at https://github.com/flutter/flutter/issues.
This started only after moving to Flutter 3.44.0, and it reproduces across operating systems.
Steps to reproduce
- Upgrade Flutter to 3.44.0 stable.
- Use an existing Flutter Android project with native plugin dependencies.
- Build a release App Bundle:
cd C:\Projects\Aya
flutter clean
flutter pub get
flutter build appbundle --release
Expected result
flutter build appbundle --release should finish successfully and generate a release .aab.
Actual result
The build fails at the very end, after bundleRelease execution time, with:
Running Gradle task 'bundleRelease'... 441,4s
Release app bundle failed to strip debug symbols from native libraries.
Please run flutter doctor and ensure that the Android toolchain does not
report any issues.
Otherwise, file an issue at https://github.com/flutter/flutter/issues.
Platform scope
- Reproduced on Windows 11
- Reproduced on macOS
- Same Flutter version: 3.44.0 stable
Flutter Doctor output (Windows)
Command:
Output:
[√] Flutter (Channel stable, 3.44.0, on Microsoft Windows [version 10.0.26200.8457], locale fr-FR) [440ms]
• Flutter version 3.44.0 on channel stable at C:\flutter
• Upstream repository https://github.com/flutter/flutter.git
• Framework revision 559ffa3f75 (6 days ago), 2026-05-15 14:13:13 -0700
• Engine revision 4c525dac5e
• Dart version 3.12.0
• DevTools version 2.57.0
• Feature flags: enable-web, enable-linux-desktop, enable-macos-desktop, enable-windows-desktop, enable-android, enable-ios, cli-animations, enable-native-assets, enable-swift-package-manager, omit-legacy-version-file,
enable-lldb-debugging, enable-uiscene-migration
[√] Windows Version (11 Professionnel 64-bit, 25H2, 2009) [1 287ms]
[√] Android toolchain - develop for Android devices (Android SDK version 36.1.0) [2,5s]
• Android SDK at C:\Android\sdk
• Emulator version 36.5.11.0 (build_id 15261927) (CL:N/A)
• Platform android-36, build-tools 36.1.0
• ANDROID_HOME = C:\Android\sdk
• ANDROID_SDK_ROOT = C:\Android\sdk
• Java binary at: C:\Program Files\Android\Android Studio\jbr\bin\java
This is the JDK bundled with the latest Android Studio installation on this machine.
To manually set the JDK path, use: `flutter config --jdk-dir="path/to/jdk"`.
• Java version OpenJDK Runtime Environment (build 21.0.10+-14961533-b1163.108)
• All Android licenses accepted.
[√] Chrome - develop for the web [144ms]
• Chrome at C:\Program Files\Google\Chrome\Application\chrome.exe
[√] Visual Studio - develop Windows apps (Visual Studio Community 2022 17.13.6) [143ms]
• Visual Studio at C:\Program Files\Microsoft Visual Studio\2022\Community
• Visual Studio Community 2022 version 17.13.35931.197
• Windows 10 SDK version 10.0.22621.0
[√] Connected device (3 available) [240ms]
• Windows (desktop) • windows • windows-x64 • Microsoft Windows [version 10.0.26200.8457]
• Chrome (web) • chrome • web-javascript • Google Chrome 148.0.7778.169
• Edge (web) • edge • web-javascript • Microsoft Edge 148.0.3967.70
[√] Network resources [295ms]
• All expected network resources are available.
• No issues found!
PS C:\Projects\Aya>
What was already tried
- Full clean before build (
flutter clean, flutter pub get)
- Rebuild in release mode repeatedly
- Validation of Android toolchain with
flutter doctor -v (no issues reported)
- Cross-platform verification (Windows and macOS): same failure
Notes
The key issue is that Flutter 3.44.0 release AAB builds now fail at the final symbol-stripping phase, despite a healthy toolchain and successful Gradle execution time, and this behavior is reproducible on multiple OSes.
Flutter 3.44.0 – Android release AAB build fails at the very end on Windows and macOS
Summary
Since upgrading to Flutter 3.44.0 (stable), Android release bundle builds fail consistently on both Windows and macOS.
The Gradle
bundleReleasetask runs for several minutes and appears to complete, but Flutter fails during the final post-build step with:This started only after moving to Flutter 3.44.0, and it reproduces across operating systems.
Steps to reproduce
Expected result
flutter build appbundle --releaseshould finish successfully and generate a release.aab.Actual result
The build fails at the very end, after
bundleReleaseexecution time, with:Platform scope
Flutter Doctor output (Windows)
Command:
flutter doctor -vOutput:
What was already tried
flutter clean,flutter pub get)flutter doctor -v(no issues reported)Notes
The key issue is that Flutter 3.44.0 release AAB builds now fail at the final symbol-stripping phase, despite a healthy toolchain and successful Gradle execution time, and this behavior is reproducible on multiple OSes.