Flutter 3.47.1: The Twelve Fixes Shipping a Week After 3.47
Flutter 3.47.1 is a conservative hotfix release covering SwiftPM races, WASM hot restart, a plugin registrant security fix, and more.
Published on • October 19, 2026
AI Assistant

Flutter 3.47.0 went stable on August 12, 2026 — “Modular by design,” with standalone material_ui and cupertino_ui packages and Impeller as the default desktop renderer. One week later, on August 19, 2026, the 3.47.1 tag landed on the repository: a small, deliberately conservative patch release in the tradition of Flutter’s hotfix policy. If you’re on 3.47.0, here’s exactly what you’re getting and why at least one of these fixes should push you to upgrade.
How Flutter patch releases work
Flutter ships feature stables quarterly, then hotfixes only when a bug or regression clearly warrants it. The policy, stated at the top of the repository CHANGELOG, is worth internalizing:
- Hotfixes are extremely conservative — “there’s always a risk that fixing one bug introduces a new one,” and stable must remain the most tested build.
- Only the latest stable version is hotfixed. Bugs on older stables aren’t backported; you move forward instead.
- Hotfixes are announced on the flutter-announce group before you’d otherwise notice them.
That’s why 3.47.1 exists as a .1 rather than a new blog post: patch releases carry curated fixes, not features. Upgrading is the usual two commands:
flutter channel stable
flutter upgrade
flutter --version # expect Flutter 3.47.1 or newer
What’s in 3.47.1
The release tag and the CHANGELOG entry list twelve fixes. Grouped by what they mean for you:
Builds and tooling
- SwiftPM race condition in parallel builds (#188446): building multi-target applications in parallel on iOS and macOS could throw a
FileSystemExceptionbecause of a race in the Swift Package Manager integration. This one bites CI hard — if your iOS pipeline shuffles build targets concurrently, 3.47.1 is your fix. - Flutter GPU in release builds on desktop (#190871): Flutter GPU couldn’t be enabled in release builds on Linux and Windows, because those embedders had no project-level opt-in and release mode ignores environment-based engine switches.
flutter pub getin Dart workspaces (#189550): platform tooling regeneration andanalysis_options.yamlmigration were skipped for workspace packages that don’t depend on Flutter.- Native asset cleanup crashes (#190234): no more
PathNotFoundExceptionwhen native asset files are removed concurrently during cleanup. - Analyzer options migration (#191056):
include:directives are now resolved recursively, preventing redundant rewrites ofanalysis_options.yaml. impellercon Windows (#190233): the shader compiler no longer crashes on paths containing Unicode characters, and shader compiler error diagnostics improved.- ADB device list parsing (#189972): long wireless mDNS serials no longer break device detection.
Hot reload, hot restart, and debugging
- WASM web hot restart (#186445): hot restart now works for WASM web builds — relevant if you’ve followed the roadmap’s push to make WebAssembly the default on web.
- Hot reload in pub workspaces (#190284): edits in nested workspace member packages under the root
lib/reload correctly now. - Debug adapter deadlock (#190721): no more deadlock when the target process exits early during startup, before the VM service connection completes.
Web plugin registration
- Web plugin registrant staleness (#189128):
WebEntrypointTargetis invalidated andweb_plugin_registrant.dartregenerated when web plugins are added or removed — meaning a new web plugin no longer silently fails to register until you manually clean.
Security
- Plugin registrant injection (#189156): plugin class and package identifiers are now validated to prevent arbitrary code injection into
GeneratedPluginRegistrant. This is a build-time hardening fix; it’s the entry on this list most worth having regardless of whether you hit any of the others.
Should you upgrade?
Upgrade promptly if any of the following describe you:
- You run iOS/macOS builds in parallel on CI (the SwiftPM race).
- You build for WASM web (hot restart).
- You use Dart pub workspaces (both
pub getand hot reload fixes). - You ship Windows builds with Unicode install paths or use Flutter GPU.
- You care about the
GeneratedPluginRegistranthardening.
If you’re still on 3.44 or 3.41, note the hotfix policy: those lines don’t get .1 patches for your bugs. Your path forward is the newest stable line — read the 3.47 breaking changes first, especially the new minimums (iOS 15, macOS 12) and the Material/Cupertino package migration.
One more thing to watch: 3.47.1 is not the end of the line for the 3.47 branch. The CHANGELOG shows subsequent patches (3.47.2 and later) addressing further regressions, so check what the current latest stable is before you pin — flutter upgrade will land you on the newest one.
Verifying what you’re running
If you manage more than one machine or CI runner, don’t assume — check:
flutter --version
# Flutter 3.47.1 • channel stable • https://github.com/flutter/flutter.git
# Framework • revision 6655482... • 2026-08-19
flutter channel stable
flutter upgrade
# Pin it in CI after verifying
flutter version 3.47.1
The 3.47.1 tag points at a single commit (6655482) signed by flutteractionsbot, which is what your CI should resolve to. The tag’s existence also tells you the hotfix made it through Flutter’s own release automation — patch releases aren’t patched-in-place; they’re cut as immutable tags you can pin against.
Treat patch adoption as a routine, low-risk chore rather than an event: because patch releases only contain conservative, cherry-picked fixes, the diff between 3.47.0 and 3.47.1 is small enough to review in a few minutes against your own test suite. The CHANGELOG entry is your review surface — each line links the exact issue it addresses.