Published November 20, 2026
Flutter 3.50.1 Lands on Stable: Dot Assets, Android Build Types, and a Wasm Freeze All Fixed
Flutter 3.50.1 was tagged on the stable channel on November 19, roughly a week after 3.50.0 shipped. The changelog carries eleven entries, which is a large hotfix by Flutter's own standards. The team describes its hotfix policy as extremely conservative, on the reasoning that fixing one bug can introduce another, so a list this long means a cluster of regressions arrived together and were serious enough to justify the risk.
Two of the entries are the kind that make a release train stop. The rest are the kind that quietly waste a developer's afternoon. Both categories are worth reading before you decide whether to run the upgrade today.
The asset bug that breaks apps at runtime
The first is issue 196444. When building for Android with 3.50.0, assets whose names begin with a dot, such as a .env file, or whose folders begin with an underscore, were silently left out of the APK and the AAB. Nothing failed at build time. Nothing warned. The failure surfaced later, at runtime, when the app asked for a file that the packaging step had decided to skip.
This is the worst shape a packaging bug can take. An error at build time costs a minute. An error at runtime costs a support ticket, an app store review cycle, and a session spent comparing a debug build that worked against a release build that did not. Teams that ship configuration files, certificates, or seed data inside their asset bundle should assume they are affected if they built with 3.50.0 and did not verify the contents of their archive.
The second entry is issue 196412. Building an Android app that uses plugins together with custom build types, or app-only build type settings, failed during Gradle configuration. The underlying fix changes how the Flutter Gradle plugin copies build types onto plugin projects: instead of a blanket initWith copy, library plugins now receive only the properties a library can legally accept, skipping application-only fields such as applicationIdSuffix that AGP rejects.
That detail matters more than it sounds. Flutter's Gradle plugin mirrors the host app's build types into every plugin subproject so their variants resolve. When a plugin is built as a library, copying an app-only property produces a configuration error rather than a variant, and the build never starts. Anyone who defines a staging or internal flavor with its own application ID suffix has probably met this already.
Web, tooling, and the rest of the list
The web fixes are narrower but no less annoying. Under --wasm with cross-origin isolation enabled, rendering dynamic text could freeze or crash the app (issue 193695). And flutter run -d chrome failed to attach to the debug service with a TimeoutException on large web apps, which is the sort of failure that reads like a network problem and is not one.
The rest of the hotfix covers:
- Linux apps shifted their content on drivers without glBlitFramebuffer support (issue 195885).
- flutter build web without --web-content-hash deleted build/web/index.html after a previous build that used the flag (issue 196452).
- flutter screenshot --type=skia crashed with an unhandled RPCError against Impeller-enabled apps (issue 196119).
- Debug launch crashed when the device or host temporary directory was full or inaccessible, most often on Windows and on the iOS Simulator (issue 196118).
- flutter test on macOS failed with a cross-device link error when the project or build directory sat on an external volume (issue 196121).
- APKs built with --split-per-abi shared one versionCode when the value was set only in AndroidManifest.xml (issue 196559).
- Gradle could not store its configuration cache entry for Android builds, so it never reused it (issue 195006).
Two of those deserve a second look from teams with release pipelines. Duplicate versionCodes across ABI splits is the sort of bug that blocks an upload to Play rather than failing a build, and the configuration cache fix is the difference between a daily Android build that takes four minutes and one that takes nine.
Should you upgrade now
Flutter only hotfixes the latest stable release. Anyone still on 3.47 is not going to receive these fixes, and the dot asset bug plus the Gradle configuration failure are both present in 3.50.0, which makes the choice closer to mandatory than usual for Android projects with plugins and custom build types.
The upgrade itself is the standard two commands on the stable channel, followed by a rebuild of every artifact you intend to ship. Run a release build of the Android app with a dot-prefixed asset in the bundle and confirm the file is inside the archive before you trust the result. Then open the app on a physical device and exercise the screen that renders dynamic text in a Wasm web build if you ship one.
For teams that just moved to 3.50 last week, this is a fast follow and a reminder of what a fresh stable line costs in the first month. The feature work in 3.50, from direct native interop to the faster Wasm output, remains intact. The hotfix is the tax on shipping it early, and eleven entries is a smaller tax than eleven silent failures.