v3.4.2 — Unstick the Android Launcher
v3.4.2 — Unstick the Android Launcher
If you're on Android and tapped "Beatify öffnen" in the Home Assistant Companion app over the last two days, you probably saw the toast pop up, said the right thing — and then nothing happened. No tab opened, no error, just the launcher screen staring back at you. That's gone.
🤖 Android HA Companion — the launcher actually launches
The launcher rework that shipped in v3.4.0 to fix iOS Companion users had the opposite effect on Android: iOS started working, Android stopped. Same code, different platform behavior, same toast either way.
In v3.4.2, the launcher recognises when it's running inside the Android Companion app and takes a different path on tap — one that actually puts you into Beatify instead of into a tab that never appears. You give up the "Beatify in its own tab" feel on Android (it loads in the same view now), but you do arrive at the game.
iPhone, desktop, and regular mobile browsers are unchanged. If it works for you today, it'll work the same way tomorrow.
🔧 Under the Hood
One file changed (launcher.html), one bug closed (#1114), one PR landed (#1116). Standard 6-file version bump 3.4.1 → 3.4.2. 96/96 tests still green. Otherwise this is the same v3.4.1 you've been running.
🙏 Thank you
To @Dtrieb for filing the report and pinning it to a specific Samsung phone, Android version, and Companion version — exactly the detail the diagnosis needed. To @nixbuongiorno for the second confirmation with the exact toast text, which proved the click was firing but the new tab wasn't. And to @markist for the one-line observation that cracked it open — "Opening Works in Brave Browser." Three reporters, two days, one-file fix.
35 playlists · 4,013 songs · 5 music platforms · 5 languages
