Type in your question below and we'll check to see what answers we can find...
Loading article...
Submitting...
If you couldn't find any answers in the previous step then we need to post your question in the community and wait for someone to respond. You'll be notified when that happens.
Simply add some detail to your question and refine the title if needed, choose the relevant category, then post.
Before we can post your question we need you to quickly make an account (or sign in if you already have one).
Don't worry - it's quick and painless! Just click below, and once you're logged in we'll bring you right back here and post your question. We'll remember what you've already typed in so you won't have to do it again.
Please see below the most popular frequently asked questions.
Loading article...
Loading faqs...
Please see below the current ongoing issues which are under investigation.
Loading issue...
Loading ongoing issues...
[Premium][iPhone 7 plus][iOS 12.2][Spotify version 8.5.3.784]
Prior to a few weeks ago I could add podcasts to my play queue, and did so happily before I started every long morning drive. Now, I can go through all the steps (find the podcast, click on the ..., select "add to queue," get the checkmark and "added to queue" message -- but there is no queue created. In the now playing screen, the box at lower right still shows the share icon, not a queue icon, there are no forward or back buttons to advance to the next/prior in the queue, and when the current podcast ends, there is no next podcast. The queue function still works just as always for songs, just not for podcasts. I have restarted the app, deleted it and reloaded it, logged out and in again. I have searched this board, and found a user in Brazil who had the same issue a month ago -- he even posted pictures! -- and never got an answer after the initial "here's how you create a queue" generic answer. Please help -- without this function it is very hard to use the app while driving. And it worked like a charm for so long....something must have been inadvertantly changed during one of these updates in which the queue function was messed with.