Meshtastic desktop bug crashes Messages on Windows 11 users report

Meshtastic pushed a fast fix into its next closed Android build after a reproducible desktop crash kept dropping Windows 11 users out of Messages. The bug hit version v2.8.0-closed.6 (29321371), and the replacement build, v2.8.0-closed.7, switched to the stored contact_key to stop the duplicate LazyColumn key failure.

The crash was easy to trigger and hard to ignore. On a Windows 11 desktop session tied to a Heltec WSL v3 node over Wi-Fi, with a node running firmware 2.7.26, clicking Messages brought up a key-collision error tied to the value "8!xxxxxxxx". Dismissing the dialog did not recover the app in any useful way. The window still had to be ended through Task Manager, which turned a simple inbox check into a full restart.

That makes the bug more than a cosmetic UI hiccup. Meshtastic’s desktop app is built for exactly the kind of work that needs stability: reading mesh traffic, replying from a laptop, and keeping an eye on notifications while a radio stays connected in the background. The project’s desktop documentation says the app can control notifications for messages, new nodes, and low-battery alerts, while the broader platform supports linking a phone or computer to a radio over Bluetooth, Wi-Fi, or USB without cell service or internet. Meshtastic also documents meshtasticd for Mac and Linux, which turns a computer into a node, and its WSL guidance shows how Windows users can reach a node through the instance IP and shared USB devices.

The fix landed in the v2.8.0-closed.7 release and was credited to jamesarich in pull request #6142. GitHub’s issue record shows the July 7 report was closed by that patch, which ties the failure directly to the next build stream rather than leaving it as an open desktop problem. For anyone checking a laptop-based setup in the field, the upgrade line is simple: if the build string still says v2.8.0-closed.6, Messages can still fall over on open.

That same release also carried broader feature work, including Site Planner coverage integration, CO sensor temperature and humidity display, and a histogram of nodes per hop distance. In a release train moving that quickly, this bug is the kind of tester-facing regression that matters most now: the Messages pane is back to being a window into the mesh, not a reason to reach for Task Manager.