v1.0.35
Fixes MDB detection on macOS 26 (Tahoe). If you are on macOS 26, this is the update you want. Windows, Linux and older macOS are unaffected, so there is nothing urgent here for you.
macOS 26 (Tahoe)
The installer reached "Flashing MDB" and then sat on "Waiting for device path" forever, with a healthy board in mass storage mode and a working ums session.
macOS 26 changed how USB devices are reported. system_profiler's USB datatype was renamed (SPUSBDataType -> SPUSBHostDataType), and the old name still exits 0 while reporting nothing, so probes looked like "no devices attached" rather than failing. The new reporter also dropped the BSD Name entries that tied a USB device to a disk. Detection needed both, so it could never resolve a flash target.
USB identity now comes from the IORegistry via ioreg, which is IOKit level and unaffected by reporter renames. system_profiler stays as a fallback for older macOS. The diagnostics panel got the same treatment, so it no longer comes up blank on macOS 26.
Reproduced and verified on macOS 26.6 (build 25G72), Apple silicon, with an unu Scooter Pro MDB.
Thanks @banglashi for the diagnosis and the fix.
Flash target safety
The USB identity cross-check that decides which disk gets written is now bounded to a single device subtree. A USB device that publishes no descriptor properties of its own can no longer inherit the gadget's identity and have its disk offered as the flash target. Relevant if you flash with other USB drives attached.
Unchanged: when identity cannot be resolved at all, the installer still refuses to select a target rather than guessing.
Build and CI
- macOS builds no longer need signing secrets to complete, so forks can produce a runnable unsigned build. Signing, notarization and stapling are skipped when their secrets are absent and run as before when they are present.
flutter testnow runs before any build, and the builds wait on it.
Full changelog: v1.0.34...v1.0.35
