NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
pub.dev
Flutter plugin for immersive 3D rendering on live maps (vehicle avatars, tracking scenes). Maintained fork of thermion_flutter 0.3.4 (Apache-2.0) with App Store native-assets fixes.
Last release 27 days ago
13 Sep 2026
Ships on a steady schedule
a new release about every 2 months
Nearly every release is documented
notes for 3 of 3 stable releases
Nothing withdrawn
no release was ever pulled
4 months old
3 releases · first in 2026
One column per month.
Forked from thermion_flutter 0.3.4 as atlas3d_flutter.
Fix: ThermionWidget could stop rendering for the rest of the process. _ThermionTextureWidgetState registers itself in a static set, and only first in
ThermionWidget could stop rendering for the rest of the process.
_ThermionTextureWidgetState registers itself in a static set, and only
first in that set calls FilamentApp.requestFrame(). Registration happened
after awaiting texture creation, with no mounted check, so a widget disposed
during that await re-added itself after dispose() had removed it. The dead
state then stayed first forever, and every later ThermionWidget stayed
blank until the app was killed. The state now releases its texture and never
registers when it is unmounted mid-setup, and it no longer touches context
after dispose.Android: pin ndkVersion to 27.0.12077973. r28 removed libc++_shared.so for the ARM triples, which atlas3d_dart's build hook must bundle, so r28 cannot
Android: pin ndkVersion to 27.0.12077973. r28 removed libc++_shared.so for
the ARM triples, which atlas3d_dart's build hook must bundle, so r28 cannot
build this package at all (see atlas3d_dart 0.3.4+4).
This pin is necessary but not sufficient. The native-assets toolchain
resolver picks its own NDK and ignores ndkVersion; if a newer NDK is
installed it will still be selected for the native build. r27 must be the NDK
the machine resolves — uninstall or move aside newer NDKs. atlas3d_dart
0.3.4+4 fails fast with an explanation when that is not the case.
Your coding agent can read these notes before it upgrades. Set up the MCP server →