dynamic_app_icon_flutter_plus

Releases

1. ▸▾2.2.13 Aug 2026

   Android — fixed a regression from 2.2.0 that left both the default and alternate launcher icons enabled simultaneously. The 2.2.0 atomic-swap rework a

   • Android — fixed a regression from 2.2.0 that left both the default and alternate launcher icons enabled simultaneously. The 2.2.0 atomic-swap rework accidentally skipped disabling MainActivity on manifests without a .default activity-alias, so switching to an alternate icon enabled the new alias without disabling MainActivity — showing duplicate launcher icons (#7). IconSwapper.applyIcon() now always disables the previous default component (MainActivity itself, for legacy manifests) unless it is the target, restoring the pre-2.2.0 single-icon behavior.

   Open source →
2. ▸▾2.2.025 Jul 2026

   Android — fixed a critical non-atomic icon swap that could leave the app fully unlaunchable. IconSwapper.applyIcon() previously disabled every launche

   • Android — fixed a critical non-atomic icon swap that could leave the app fully unlaunchable. IconSwapper.applyIcon() previously disabled every launcher component before enabling the target one. If the process was killed mid-swap — most likely exactly when the swap is deferred to onTaskRemoved/onDestroy via deferUntilBackground — the app could end up with zero enabled, exported launcher components: no icon, unlaunchable except through system settings ("App info") followed by a reinstall. The swap now enables the target component first and disables the others after, so there is never a moment with no enabled launcher component, no matter when the process dies.
   • Android — MainActivity is no longer disabled during an icon swap when a .default activity-alias is declared. Toggling MainActivity itself (the previous behavior) could break deep links, App Links, and notification-tap handling while an alternate icon was active, and could crash on flavor builds using applicationIdSuffix. Declare a package.MainActivity.default activity-alias to own the launcher entry (see the updated Android Setup instructions and the example app's manifest) and MainActivity will never be toggled again. Manifests without a .default alias keep the old behavior (MainActivity is toggled) — this is a non-breaking, opt-in migration.
   • Android: Added a self-healing safety net — if an icon swap somehow leaves no launcher component enabled, the default component is automatically re-enabled rather than leaving the app bricked.
   • Updated the example app's manifest to use the new .default alias pattern, plus a debug-source-set manifest overlay (example/android/app/src/debug/AndroidManifest.xml) that restores MainActivity's launcher intent-filter for flutter run/flutter attach compatibility, since Flutter's tooling launches MainActivity directly and doesn't resolve activity-aliases.