Flutter 3.50 upgrade plan: 7 breaking changes for teams on 3.44 and 3.47

Flutter 3.50 deprecates in-SDK Material, hardens Android intents and opens Wasm to Safari and Firefox. Target 3.50.1 and audit intents first.

Read time
16 min
Word count
2.4K
Sections
12
FAQs
8
Share
Two engineers compare test cards beside a laptop, phone and tablet, with Flutter and Dart logos and 3.50 upgrade text
On this page · 12 sections
  1. What shipped on 11 November, and the 20 November hotfix
  2. Break 1: the Material and Cupertino deprecation
  3. Break 2: stricter Android intent checks
  4. Break 3: the web changes
  5. Direct native interop: stable, but not a forced move
  6. Android build toolchain defaults
  7. iOS and macOS changes
  8. Dart 3.14 and the dart migrate tool
  9. The upgrade plan, in order
  10. India-specific considerations
  11. How eCorpIT can help
  12. References

Summary. Flutter 3.50 and Dart 3.14 became the stable releases on 11 November 2026, and the first hotfix, 3.50.1, followed on 20 November. For teams still on 3.44 (May 2026) or 3.47 (August 2026), three changes matter most. The bundled Material and Cupertino libraries are formally deprecated, and flutter create now starts new apps on the standalone material_ui package. Android release builds ignore route, entrypoint and cached-engine extras sent by other apps, and drop engine flags passed through intents. Direct native interop is stable, with FFIgen for Objective-C and JNIgen for Java and Kotlin. On the web, Wasm builds can run in Safari 26.2 and later and Firefox 147 and later if you opt in. The breaking-changes index lists 7 items for 3.50. Our verdict: target 3.50.1, not 3.50.0, because the hotfix restores Android assets with dot-prefixed names or underscore folders that 3.50.0 silently left out of APKs and app bundles. Audit Android intents first, and schedule the upgrade for December rather than a release week.

About this article. This is for CTOs, mobile leads and Flutter engineers who own production apps on Flutter 3.44 or 3.47. On 21 November 2026 we checked every version, flag, default and date against the Flutter and Dart announcements, release notes, hotfix changelog and documentation, and Google Play's target API policy. Point releases can change defaults, so recheck the release notes before you start. This is general engineering information, not security advice for your app, and no vendor paid for inclusion. Researched with AI assistance and checked against the primary sources listed in the references.

What shipped on 11 November, and the 20 November hotfix

Flutter 3.50 shipped alongside Dart 3.14. The Flutter team says 188 contributors, 69 of them first-timers, landed more than 1,200 commits in this cycle. The breaking-changes index lists seven items under 3.50, and the announcement adds two framework clean-ups.

Area What changed in 3.50 Who has to act
Design libraries In-SDK Material and Cupertino deprecated; new apps import material_ui Every app, over time
Android intents Release builds ignore external route, entrypoint and cached-engine extras Apps with exported Flutter activities
Android engine flags Release builds ignore engine flags in intents; the CLI refuses them for a prebuilt release binary QA and test pipelines
Native interop FFIgen (Objective-C) and JNIgen stable; Pigeon interop mode in preview Plugin and SDK teams
Web Wasm opt-in for Safari 26.2+ and Firefox 147+; content hashing; legacy JS interop deprecated Flutter web apps
Web layout SafeArea honours viewport-fit=cover on mobile browsers Web apps with that meta tag
Text and widgets Soft hyphens shown at line breaks; WidgetSpan order fixed in right-to-left text; dropdown enabled flag Apps with long words, Arabic or Hebrew UI
Tooling Warning when Swift Package Manager is off; warning on Intel Macs iOS and macOS build machines

The table summarises the 3.50 announcement and the breaking-changes index.

The 3.50.1 hotfix matters too. The Flutter changelog says it fixes Android builds that dropped assets such as .env files or underscore folders from the APK or AAB, Gradle configuration failures for apps with plugins and custom build types, split-per-ABI APKs sharing one version code when it was set only in the manifest, and a Wasm freeze when rendering dynamic text with cross-origin isolation on. A plain flutter upgrade on stable now lands on 3.50.1. Pin it, or later, in CI.

Break 1: the Material and Cupertino deprecation

This is the change every Flutter app will eventually touch. Contributions to the in-SDK Material and Cupertino libraries were frozen from 3.44, the standalone packages reached 1.0 in 3.47, and 3.50 formally deprecates the old imports along with their localisation delegates in flutter_localizations. The 1.0 packages match the frozen framework code, later versions follow semantic versioning, and the Flutter team plans weekly releases.

Deprecated does not mean removed. Your 3.44 or 3.47 code still compiles on 3.50, but expect deprecation warnings on the old imports.

The migration has an automated path:


            dart fix --apply --code=migrate_design_widgets
# only if dart fix did not add the packages to pubspec.yaml
flutter pub add material_ui
flutter pub add cupertino_ui
# second pass for remaining fixes and import sorting
dart fix --apply
          

The fix rewrites imports to package:material_ui/material_ui.dart and package:cupertino_ui/cupertino_ui.dart.

The catch is third-party packages. While dependencies still import the old libraries, MaterialUiCompatibilityBridge, placed inside MaterialApp.builder, lets unmigrated widgets read theme and localisation data from context. It cannot fix type clashes. If a dependency takes or returns SDK types such as ColorScheme or TextTheme in its public API, values from the old library will not assign to parameters typed from material_ui, so that dependency has to migrate first. The Flutter docs tell package authors to treat the switch as a major version bump, so expect new major versions of UI packages.

Run the fix on a branch, list every dependency that still imports package:flutter/material.dart, and track any with API-signature coupling as a blocker. Our earlier material_ui migration guide covers the background to the freeze.

One small API change sits inside material_ui 1.8.0: DropdownButtonFormField gains an explicit enabled parameter and onChanged becomes optional, so you no longer disable a dropdown by passing null.

Break 2: stricter Android intent checks

This is the change most likely to break something in production without a compiler error, so audit it first.

Until 3.50, the Android embedder (FlutterActivity and FlutterFragmentActivity) accepted routing, entrypoint and engine settings straight from intent extras. The Flutter docs say this let other apps push navigation to sensitive internal routes, run arbitrary Dart entrypoints, or reuse an engine that was already signed in.

In 3.50 release builds, the embedder checks the sender before it reads five extras: route, dart_entrypoint, dart_entrypoint_args, cached_engine_id and cached_engine_group_id. An intent counts as trusted when:

  • the activity is not exported (android:exported set to false);
  • on Android 14 (API 34) and later, the launching UID matches the app's own UID;
  • on Android 13 and earlier, the calling package matches the app, which needs a launch through startActivityForResult() or startActivityIfNeeded().

Deep links still work, but the URI must match an intent filter in your manifest unless the intent is self-sent. When verification fails, the extras are ignored: the initial route falls back to command-line arguments, manifest metadata or /, the entrypoint falls back to manifest metadata or main, and the arguments and cached-engine IDs return null. Debug and profile builds skip the check but log a warning.

Pattern in your app Effect in a 3.50 release build Fix
Notification taps that set EXTRA_INITIAL_ROUTE on an exported activity Route ignored; app opens at the default route Send a deep link with ACTION_VIEW matching an intent filter
Add-to-app host launching a cached engine from another module Cached engine ID ignored if the sender is not verified Make the host activity non-exported, or launch from the same app UID
Partner app or widget opening a screen by route extra Extra ignored Publish a deep link contract instead
Exported launcher activity with no extras No change None; the launcher must stay exported

The table follows the migration guidance on the Flutter breaking-change page.

The companion change hits test pipelines. Release builds now ignore engine flags such as --dart-flags passed through intent extras, and the Flutter CLI stops with a fatal error if you pass engine flags to a prebuilt release binary with flutter run --release --use-application-binary. Standard release builds are unaffected because the CLI writes flags into the manifest at compile time. If your QA farm injects flags into release APKs, or you build with Bazel, move those runs to profile mode or a fresh build.

Break 3: the web changes

Flutter web apps get four changes at once.

Wasm in Safari and Firefox. flutter build web --wasm builds both a WebAssembly and a JavaScript bundle and falls back to JavaScript where Wasm cannot run. Chromium browsers from version 137 run Wasm by default. Safari 26.2 and later (macOS and iOS) and Firefox 147 and later still fall back to JavaScript unless you allow them in web/flutter_bootstrap.js; the Flutter team plans to switch them on in a later stable release and reports more than twice the frame rate of JavaScript on heavy widget benchmarks. The docs group all iOS browsers under WebKit, so that switch covers Chrome and Firefox on iPhone too.


            {{flutter_js}}
{{flutter_build_config}}

_flutter.loader.load({
  config: {
    wasmAllowList: { blink: true, webkit: true, gecko: true },
  },
});
          

The snippet follows the opt-in in the 3.50 announcement. Test on real iPhones before you switch it on.

Legacy JS interop is deprecated. dart:html, dart:js, dart:js_util and package:js are deprecated in favour of dart:js_interop and package:web, Dart says they will be removed in an upcoming SDK release, and they already do not work on Wasm targets. Build with --no-deprecated-js-interop to fail early if your app or any package still imports them.

Content hashing. flutter build web --web-content-hash adds an eight-character content hash to compiled entrypoints and asset filenames, so you can cache them for a year and keep index.html and flutter_bootstrap.js uncached. It also writes a precache manifest for custom service workers. On 3.50.0, a normal build after a hashed build deleted index.html from the output; 3.50.1 fixes it.

SafeArea on mobile browsers. If your web/index.html already sets viewport-fit=cover, the engine no longer strips it, so your app draws edge to edge behind notches and home indicators, and SafeArea reads the browser's safe-area insets. Check every web screen that sits at the top or bottom of the viewport.

Our Flutter web Wasm production guide covers server headers and rollout in more depth.

Direct native interop: stable, but not a forced move

FFIgen for Objective-C and JNIgen for Java and Kotlin are now stable, joining FFIgen's C support. They generate Dart bindings so you can call platform APIs directly, including synchronously and from background isolates, instead of serialising messages over platform channels. Pigeon has a new native interop mode in preview that uses both generators. The Flutter interop docs describe these as low-level bindings that leave native memory lifetimes and threading to you.

Platform channels are not deprecated, so do not rewrite working ones during the 3.50 move. Use FFIgen or JNIgen for new plugins, for hot paths where channel latency shows up in profiling, and for code that needs a synchronous answer. Keep Pigeon's interop mode out of production until it leaves preview.

Android build toolchain defaults

New Android projects generated by 3.50 use AGP 9.3.1 and Gradle 9.5.0, tested against Kotlin Gradle Plugin 2.4.20 and at least Java 17, with compile and target SDK 36 and minimum SDK 24. Existing projects keep their own settings. Since 31 August 2026, Google Play has required new apps and app updates to target API 36 or higher, apart from Wear OS, Automotive, TV and XR apps.

Between 3.47 and 3.50 the Flutter Gradle Plugin was rewritten against the public AGP 9 APIs, and on 3.50 you can opt into AGP 9's new DSL once every plugin in the project supports Built-in Kotlin. Built-in Kotlin is switched on with android.builtInKotlin=true in gradle.properties and needs AGP 9 and Flutter 3.47 or later, so 3.44 teams cannot enable it before upgrading. Plugins that still apply the Kotlin Gradle Plugin by hand will fail to build under AGP 10, according to the Flutter team. Our AGP 9 and Flutter 3.47 guide walks through the plugin audit.

iOS and macOS changes

  • Swift Package Manager. CocoaPods trunk stops accepting new podspecs permanently on 2 December 2026, and 3.50 warns on every Flutter command if Swift Package Manager is disabled. A later release removes the opt-out and then the CocoaPods fallback. If you turned it off to get round a build error, turn it back on now. Our CocoaPods sunset playbook has the steps.
  • iOS 27 debugging. flutter run no longer stalls on a white screen on a newly paired or upgraded iPhone, intermittent launch crashes on iOS 27 devices are fixed, and flutter screenshot works on physical devices when you build with Xcode 27. Some of these fixes already reached 3.47 through the 3.47.4 and 3.47.5 hotfixes.
  • Touch latency. Touch events now reach the framework in the same display refresh, cutting input latency by one frame: 16 ms at 60 Hz and 8 ms on 120 Hz screens, by the Flutter team's measure.
  • Intel Macs. Flutter no longer tests on Intel Mac hardware and warns once on Intel hosts. A future release will require Apple Silicon to build for iOS, macOS or Android. The Flutter team's deprecation design proposal pencils in April or May 2027 for ending development on Intel Macs, so plan to replace Intel build machines early next year.
  • Native assets. The minimum iOS version for native assets builds rises from 13 to 15, a change also hotfixed into 3.47.4. Check this if you ship code assets through build hooks.

Dart 3.14 and the dart migrate tool

Dart 3.14 adds dart migrate, which moves a package forward one SDK version at a time: it applies preparatory fixes, bumps the SDK lower bound in pubspec.yaml, and offers optional clean-up fixes. The Dart team's example removes final from parameters, which the post says is a compile-time error in Dart 3.13. That matters if your 3.44 app still sits on a 3.12 SDK constraint, since 3.44 shipped with Dart 3.12.


            dart migrate --dry-run
dart migrate --apply --step=prepare
dart migrate --apply --step=bump,cleanup
dart migrate --apply --target-sdk=3.14.0
          

The commands follow the Dart 3.14 announcement; the tool supports packages whose constraint already requires Dart 3.0 or later.

The upgrade plan, in order

The order puts the silent runtime risks first and the noisy but safe deprecations last.

Step Task From 3.44 From 3.47
1 Grep for the five intent extras and list exported Flutter activities Required Required
2 Move external routing to manifest deep links; mark host activities non-exported Required if step 1 finds any Required if step 1 finds any
3 Remove engine-flag injection from release QA runs Required Required
4 Upgrade to 3.50.1 or later on a branch; run dart migrate with --dry-run Covers Dart 3.12 to 3.14 Covers Dart 3.13 to 3.14
5 Run dart fix for material_ui and cupertino_ui; list blocking dependencies Packages new to you Packages already at 1.0
6 Web only: build with --no-deprecated-js-interop, check SafeArea, trial Wasm on Safari Required for web apps Required for web apps
7 Re-enable Swift Package Manager; check Intel build hosts Required Required
8 Check the APK or AAB still contains dot-prefixed and underscore-folder assets Required Required
9 Release to an internal track, then staged rollout Required Required

The steps are our synthesis of the breaking-change pages, changelog and announcements.

Keep your current version on the release branch until 3.50.1 passes a full regression run, and read the changelog for any further 3.50 hotfix before a store submission. If you are still on 3.44, our Flutter 3.44 upgrade guide covers the changes you skipped in 3.47.

India-specific considerations

Most Indian consumer apps are Android-first, with notification taps and partner integrations that open specific screens. That is where route extras hide, so run the intent audit across every Android entry point, including payment and messaging SDKs that launch your activity. For fintech and health apps holding personal data under the DPDP Act, a reused, signed-in engine is exactly the exposure you want closed.

Hybrid Composition++ for platform views is still off by default on stable and needs Android 14 (API 34) with Impeller on Vulkan, so budget phones fall back to your current mode; test maps and web views on a low-end device as well as a flagship. For Indic scripts on the web, the 3.50 WebParagraph preview lets the browser shape system fonts, which the Flutter team says avoids missing-character boxes and cuts the CanvasKit download from 5.46 MB to about 3.75 MB. It relies on an experimental Chrome API, so treat it as a trial.

How eCorpIT can help

eCorpIT is a Gurugram-based technology organisation, founded in 2021, assessed at CMMI Level 5 and MSME certified, with senior-led engineering teams working across AWS, Microsoft and Google platforms. Our Flutter developers can run the 3.50 upgrade as a scoped project, from the Android intent audit and material_ui migration to web Wasm trials and a staged store release. Talk to us at /contact-us/.

Last updated: 21 November 2026.

References

  1. What's new in Flutter 3.50, 11 November 2026 — Flutter blog
  1. Announcing Dart 3.14, 11 November 2026 — Dart blog
  1. Flutter SDK releases manifest for macOS — Flutter (Google)
  1. What's new in Flutter 3.44, 20 May 2026 — Flutter blog
  1. What's new in Flutter 3.47, 12 August 2026 — Flutter blog
  1. Migrate to standalone material_ui and cupertino_ui packages — Flutter documentation
  1. Stricter Android Intent verification for app entrypoints — Flutter documentation
  1. Restrict Android engine flags in release mode — Flutter documentation
  1. Support for WebAssembly (Wasm) — Flutter documentation
  1. Breaking changes and migration guides — Flutter documentation
  1. Flutter CHANGELOG, stable branch (3.50.1 and 3.47 hotfixes) — Flutter on GitHub
  1. JavaScript interoperability — Dart documentation
  1. Build and release a web app — Flutter documentation
  1. Web viewport-fit=cover SafeArea support — Flutter documentation
  1. Native interop — Flutter documentation
  1. Target API level requirements for Google Play apps — Play Console Help
  1. Built-in Kotlin migration for app developers — Flutter documentation
  1. CocoaPods Trunk read-only plan — CocoaPods blog
  1. Swift Package Manager for plugin authors — Flutter documentation
  1. macOS Intel deprecation strategy for Flutter (design proposal, May 2026) — Flutter team
  1. Flutter 3.50.0 release notes — Flutter documentation

Frequently asked

Quick answers.

01 When was Flutter 3.50 released?
Flutter 3.50 became the stable release on 11 November 2026, alongside Dart 3.14, and the first hotfix, 3.50.1, followed on 20 November. It follows Flutter 3.47 from August 2026 and Flutter 3.44 from May 2026, so those teams are one or two releases behind.
02 Should we ship with 3.50.0 or 3.50.1?
Use 3.50.1 or later. The hotfix fixes Android builds that silently dropped dot-prefixed or underscore-folder assets, Gradle failures with custom build types, duplicate version codes in split APKs, and a Wasm freeze on cross-origin isolated sites. A stable upgrade now lands on 3.50.1.
03 Do I have to migrate to material_ui now?
No. The in-SDK Material and Cupertino libraries are deprecated in 3.50, not removed, so existing code still compiles with deprecation warnings. Start the migration on a branch now, because third-party packages with type-level coupling to the old libraries can block you later.
04 What breaks with the stricter Android intent checks?
In release builds, Flutter ignores route, entrypoint, entrypoint argument and cached engine extras sent by other apps to an exported Flutter activity, so the app opens at its default route. Deep links matching a manifest intent filter keep working, and debug builds only log a warning.
05 Is Wasm on by default in Safari and Firefox now?
No. Flutter 3.50 supports Wasm in Safari 26.2 and later and Firefox 147 and later, but both fall back to JavaScript unless you allow them in the web bootstrap file. Chromium browsers from version 137 run Wasm by default, and the others are planned for a later release.
06 Should we replace platform channels with FFIgen and JNIgen?
Not as part of an upgrade. Platform channels still work and are not deprecated. Use FFIgen and JNIgen for new plugins, latency-sensitive paths and synchronous calls. Pigeon's native interop mode is still a preview, so keep it out of production code until it becomes stable.
07 Does Flutter 3.50 change our Android SDK targets?
Only for newly generated projects, which default to compile and target SDK 36, minimum SDK 24, AGP 9.3.1 and Gradle 9.5.0. Existing projects keep their Gradle values. Google Play has required new apps and updates to target API 36 since 31 August 2026.
08 How long should a 3.47 to 3.50 upgrade take?
It depends on exported Android activities, web usage and dependency count, so there is no single figure. A mobile-only app with no intent extras and current packages is mostly the material_ui fix and a regression run. Add-to-app hosts, legacy web interop or stale plugins add time.

About the author

Manu Shukla

Founder & Director

Founder of eCorpIT. Hands-on engineer leading senior-only delivery for AI apps, custom software, and cloud systems for global clients.

Subscribe

One engineering note a week. No fluff, no spam.

Senior-architect playbooks on AI agents, mobile apps, cloud, security, data, and marketing — delivered every Wednesday.

Past the reading

Read enough. Let's build something.

A senior architect responds in 24 working hours with scope, indicative cost, and a timeline. NDA before any technical conversation.

Loading search…

Browse all guides