Podcasts will not play

Solved!
Reply

Podcasts will not play

whodatchristine
Regular
  • Having issue playing Podcasts, but all my music is fine whether my personal playlist or a Spotify playlist.  Tried accessing old episodes of my current Podcast binge, and episodes of my older binges, and nothing! Even tried one that I had never listened to and still no playback.
  • Was able to replicate on Android, but initial issue was on Windows Desktop.
  • Not sure if relevant, but was also getting the error at the top of the desktop app when accessing the original podcast episode. "Can't play right now, Sorry! You can't play this content while connected to another device."

 

1 ACCEPTED SOLUTION

Accepted Solutions
Solution!

Re: Podcasts will not play

whodatchristine
Regular

And in the strangest turn of events, my podcasts are working again. Guess it was a temp glitch, but glad I wasn't the only one with the problem. Closing this community issue.

2 Replies

Re: Podcasts will not play

PDXJOR
Casual Listener

I'm experiencing this as well. I've tried the same podcasts on the web version and I have the same results. Oddly, only some podcasts are affected: I cannot play any episodes from The Gist or Lovett or Leave it, while I can play any episode from Planet Money and Today Explained.

 

When I try to play an episode, it will not start and just stay unplayed at the 0:00 marker, then if I attempt to play  the episode again (by double clicking on the episode name) it will give me the same error message "Sorry! You can't play this content while connected to another device". 

 

While I have Spotify on my phone and other devices, I'm 100% sure that no other devices are playing with my account. Again, immediately after I get the "Sorry!" message, I attempt to play a podcast that I mentioned earlier, I have no issues playing it.

 

Spotify Free - WIN 10 - Spotify Build 1.1.12.449.g4109e645

Solution!

Re: Podcasts will not play

whodatchristine
Regular

And in the strangest turn of events, my podcasts are working again. Guess it was a temp glitch, but glad I wasn't the only one with the problem. Closing this community issue.

SUGGESTED POSTS