What’s New in Flutter 3.50: Should You Upgrade?

Short answer: Flutter 3.50 is mostly a platform-alignment release. According to the official release notes, it raises the minimum Android Gradle Plugin (AGP) to 9.1.1 and updates templates for Android 17, deprecates more Material and Cupertino code that is moving out of the core framework, and continues multi-window work on desktop. If you target Android 17 or use AGP 9, plan to upgrade soon; otherwise upgrade once your plugins support it.

This guide summarizes the changes that matter for app developers, then gives a safe upgrade checklist. Read the full Flutter 3.50.0 release notes for the complete list.

How to get Flutter 3.50

flutter upgrade
flutter --version
flutter doctor

Confirm that flutter --version shows 3.50 before you start. Flutter now publishes public release windows, and 3.50 was scheduled for November 2026.

Android: AGP 9 and Android 17

  • Minimum AGP raised to 9.1.1, with the engine and templates moved to newer AGP versions (the notes mention AGP 9.3.1 for Android 17 templates).
  • Android 17 (API 37): Flutter stops using ReLinker to load libflutter.so on API 37 and above, and default SDK targets are being updated to 37.
  • Hybrid Composition++ (HCPP): a feature flag was added and is on by default in beta and master, with a new --[no-]enable-hcpp build flag.
  • Security: the Android embedding now refuses to let external Intents set the engine entrypoint or cached engine arguments.
  • Build tooling: engine tests now run against JDK 25.

If your project still uses an older Gradle setup, plan the AGP 9 migration first. Our Android tutorials and the screen orientation guide cover related Android 17 changes.

Material and Cupertino: more deprecations

Flutter is moving the Material and Cupertino design libraries out of the core framework. In 3.50 the notes list deprecations of the design libraries and of decoupled localizations, with dart fix support, plus updated docs and error messages. Run this after upgrading:

dart fix --dry-run
dart fix --apply
flutter analyze

New and improved framework features

Examples listed in the notes include:

  • SliverClipRect and SliverClipRRect
  • itemExtentBuilder support in ListView.separated
  • barrierBuilder for showDialog and showGeneralDialog
  • blendMode on RawImage and RenderImage
  • AutofillHints.emailOTPCode for Android email one-time codes
  • Reduce-motion accessibility support in MediaQuery
  • useLogicalPixels for ResizeImage
  • A numeric-password variation for TextInputType on Android
  • Placeholder support for DecorationImage and a FadeInImageTransition option
  • Reactive ScrollPhysics through shouldUpdate, and a dedicated rubber band spring for BouncingScrollPhysics

Desktop and windowing

The windowing API continues to evolve: classes were renamed (for example RegularWindow* to Window*), and there is more work for multi-window support on Windows, macOS and Linux, including satellite windows on Win32.

Web

The notes mention WebAssembly deferred loading, a --web-content-hash option for cache busting, many text and accessibility fixes, and a warning in dry runs about the possible future removal of dart:html. If you ship Flutter web, review your use of dart:html now.

Tooling

  • flutter test --preset and boolean tag selectors
  • flutter channel --force
  • The deprecation of the --build and --no-build flags on flutter run
  • An analyzer plugin (flutter_analyzer_plugin) that takes over some internal lint rules
  • iOS native assets minimum version raised from 13 to 15

Upgrade checklist

  1. Commit your work and create an upgrade branch.
  2. Run flutter upgrade, then flutter doctor.
  3. Run flutter pub upgrade --major-versions and check that your key plugins support 3.50.
  4. Check your Android setup: AGP 9.1.1 or newer, a supported Gradle and a current JDK.
  5. Run dart fix --apply and flutter analyze.
  6. Run your tests, then test a release build on at least one real Android and one iOS device.
  7. If you target Android 17, test on an Android 17 emulator or device.

Should you upgrade now?

  • Yes, soon if you target Android 17, use AGP 9 or need the new framework features.
  • Wait a little if a critical plugin does not yet declare support for 3.50, or if your release is close.
  • Always try the upgrade on a branch first.

Still choosing a framework? Read our Flutter vs React Native comparison, or start with the Flutter tutorial.

FAQ

What is new in Flutter 3.50?

The release notes highlight Android AGP 9 and Android 17 alignment, more Material and Cupertino deprecations, multi-window desktop work, web and accessibility fixes, and new framework APIs.

Does Flutter 3.50 support Android 17?

The notes list Android 17 related changes, including updated templates and the library loading change for API 37 and above. Test your own app on Android 17 before you ship.

Will Flutter 3.50 break my app?

Most apps should upgrade cleanly, but deprecations and the AGP requirement can need changes. Use the checklist above on a branch.

How do I check my Flutter version?

Run flutter --version in a terminal.