Your Nest speakers are on. Tidal can see them. YouTube Music can see them. Google Assistant can even start playing Spotify on them by voice. But open the Spotify Android app and tap the Connect menu, nothing appears. The Spotify Google Cast bug hitting Android users right now isn't a network problem or a hardware failure. The available evidence points to a Spotify-side regression, likely tied to a recent Android app update.
Spotify acknowledged the issue in its Ongoing Issues forum, saying it had received reports from Android users that Google Cast and Chromecast speaker devices were failing to appear in Spotify Connect. Spotify has not explained the root cause, but it has since said a new update should clear the issue and told users to watch for Spotify version 9.1.48. In a later update to the same thread, Spotify said a new update should clear the issue and told users to watch for Spotify version 9.1.48; PiunikaWeb reported that the update was scheduled to begin rolling out the week of May 18, 2026.
Android Authority reported that the issue first appeared in Spotify community posts in 2024, with reports surging recently across Reddit and Spotify support channels. The reports suggest a gradual degradation for at least some users, with intermittent early failures giving way to more consistent missing-device behavior.
If your Cast speakers have gone missing from Spotify Connect, router reboots and cache clears are unlikely to help. User reports consistently indicate those steps don't address this specific issue. The most accessible workaround is starting playback through Google Assistant or the Google Home app, then managing the queue from Spotify. Before considering riskier workarounds, affected users should check whether Spotify version 9.1.48 is available; Spotify says that update should clear the issue. Some users have also reported that rolling back the Android app to an older version restores Cast visibility, but that carries real tradeoffs.
Spotify's acknowledgment specifically references Android users. 9to5Google reported that the problem may be affecting all Spotify platforms, but that remains unconfirmed. This article focuses on Android, where the reporting is clearest.
What the Spotify Google Cast bug looks like on affected devices
The cross-app behavior is the most direct diagnostic available. Android Authority reported that Tidal, YouTube Music, and Plex all continue to find and stream to the same Cast devices that Spotify cannot see. That makes a general network or hardware failure less likely.
Google Assistant voice commands add another data point. Telling Assistant to play Spotify on a specific speaker still works even when Spotify's app shows that speaker as absent, per Android Authority. Cast discovery works. Spotify's app-side path to it apparently does not.
The iPhone-versus-Android asymmetry reported in Spotify's support forum makes the network explanation even harder to sustain. One user found that friends' iPhones could see a Cast-enabled speaker on the same home network while two Samsung Galaxy S24 Ultra phones, including a brand-new replacement unit, could not, per Android Authority. Two different Galaxy S24 Ultras failing where an iPhone succeeds on the same network makes a router-only explanation unlikely.
The clearest signal: rolling back the Android Spotify app to older builds restores full Cast device visibility, Android Authority reported. Older versions working where newer ones fail is about as direct a regression indicator as you get, though Spotify hasn't publicly confirmed what changed or when.
Spotify's standard troubleshooting guidance recommends restarting the app, restarting your Wi-Fi, and trying a different Wi-Fi network, per the Spotify support page. Forum moderators escalated to signing out everywhere and revoking access to connected third-party apps. Multiple users report none of it made any difference for this particular problem, per Android Authority. The gap between what Spotify recommends and what actually works here is worth being direct about.
What to try right now
Start with Google Assistant or Google Home. Asking Google Assistant to play music through a specific speaker on Spotify, or initiating playback via the Google Home app, can sometimes prompt Spotify's controls to recognize the device, allowing normal queue management from that point, Android Authority reported. It's inconsistent, and it doesn't fix the underlying discovery problem. But it requires nothing beyond what most affected users already have set up, which makes it the sensible first attempt.
Use the rollback option only if you know what you're doing. Users on the truespotify subreddit found that downgrading to Spotify versions 9.1.40.1486 or 9.1.42.1107, available via APKMirror, restores Cast device visibility, Android Authority reported. This is a community-discovered workaround, not something Spotify has endorsed or tested.
Anyone who isn't comfortable sideloading APKs, relies on automatic updates, or treats security hygiene as a priority should skip this entirely. Installing from APKMirror requires enabling installation from unknown sources, pins you to an outdated build instead of Spotify's expected 9.1.48 fix path, and offers no guarantee of consistent behavior across different device configurations. Last resort, not a recommendation.
Do not spend too much time on standard fixes if other apps can still see the same Cast devices. Reinstalling Spotify, clearing the cache, rebooting the router, or switching Wi-Fi networks — these steps may help ordinary connection problems, but user reports indicate those steps have not reliably resolved this Spotify-specific bug, per Android Authority.
What Spotify hasn't answered yet
Spotify has now gone beyond its initial investigation-only statement. The company still has not publicly explained the root cause or identified which app change introduced the regression, but it says a new update should clear the issue and told users to watch for Spotify version 9.1.48.
The questions that matter most remain open: whether the issue is limited to Android or extends more broadly, which app update introduced the regression, and whether version 9.1.48 fully resolves the bug across different Cast speaker setups.
The fix path Spotify has identified is an app update: version 9.1.48. Spotify has been posting acknowledgments to its Ongoing Issues forum thread, which is worth monitoring for any status change. A confirmation that the problem extends to iOS or desktop clients would also be meaningful; it would shift the diagnosis away from an Android-specific regression toward something deeper in Spotify's infrastructure.
Comments
Be the first, drop a comment!