Spotify wipes your own music off android auto and stays silent
Your carefully-curated MP3s have become ghosts the moment you plug into Android Auto. Spotify’s local-file tracks still live on the phone, still play inside the app, but vanish from every car playlist without warning.
The bug that only strikes when you're driving
Reddit user PM_me_ur_launch_code noticed it first: 47 self-ripped songs evaporated from the dash view overnight. Tap the same list on the handset and every track is there. Fire up Android Auto and the entries are replaced by blank rows that can’t be scrolled, selected or shouted back to life via Google Assistant. Album art disappears too, leaving a grid of gray placeholders where cover art once rotated.
The thread exploded. Same car, different phone? Gone. Same phone, different car? Also gone. Pixel 8, Galaxy S23, OnePlus 11—no brand escapes. Wipe cache, reinstall Android Auto, sacrifice a playlist and rebuild it bar by bar: zero fixes. Spotify Support answers with radio silence; Google’s issue tracker is a desert.
Why this is more than a niche headache
Local files are the loophole that kept die-hard collectors inside Spotify’s walled garden. Bootlegs, remixes, 24-bit masters—if you could drop it in a desktop folder, Spotify would sync it to mobile and pretend it was part of the streaming catalog. Strip that away in the one place people actually listen to uninterrupted music—commutes, road trips, cab shifts—and the value proposition collapses.
Meanwhile, Android Auto can’t stop tripping over its own updates. A steering-wheel control regression in v16.0, USB handshake failures on Pixel 9, and now a content-filtering glitch that looks suspiciously like a rights-management misfire. Add Galaxy S26 owners reporting random disconnects and the platform feels held together by firmware duct tape.
Who broke it—spotify or google?
Code sleuths on XDA point to a change in the MediaBrowserService API introduced in Android Auto 13.2. Spotify appears to flag local tracks with a private URI scheme that the latest car protocol no longer resolves. Google’s release notes mention “enhanced content security,” a phrase that usually translates to stricter license checks. Translation: either Spotify forgot to update its metadata wrapper, or Google quietly stopped accepting sideloaded audio tokens.
Neither company will own the screw-up. Spotify’s status page shows all services operational; Google’s issue tracker labels the ticket “needs more info” despite 300-plus confirmations. The stalemate leaves users circling back to prehistoric solutions: Bluetooth direct, USB sticks, or—heaven forbid—burning a CD.
Until someone admits fault, the only workaround is to start the playlist on the phone, then frantically stab “Now Playing” before the screen locks. Clunky, illegal in most jurisdictions, and a recipe for skipping the first 30 seconds of every song while you fumble for the home button.
Bottom line: if your library lives halfway between the cloud and your hard drive, Android Auto just became a $50,000 mute button. And the companies cashing your monthly fee are too busy blaming each other to press play.