Help Wizard

Step 1


Play release radar on other device doesn't prompt update

Play release radar on other device doesn't prompt update

Operating System

macOS Ventura Version 13.3.1


My Question or Issue

By my observations, the songs in release radar update (when one is available) on explicit navigation to the playlist. When listening to the updated version of release radar on a device, and then delegating it to another one (via "play on ...") that hasn't explicitly navigated to release radar yet (thus hasn't downloaded the updated list), it plays the old song at the corresponding index. 


Tested with android smartphone to macos app

3 Replies

Hey there @maximilianmairinger


Thanks for getting in touch about this here in the Community. 


Just to confirm, does this only happen with Release radar or with other playlists as well? We'd also like to know if this happens only when using the Connect feature and if it happens on any device. 


Additionally, would you mind sending us a short video of this behavior happening so we can take a closer look? You can attach it to your next response by using the Insert Video option in the post editor. You can also upload it to Google Drive and share the link with us (make sure the video has the permissions for anyone to see it).

We'll be waiting for your reply. 

Help others find this answer and click "Accept as Solution".
If you appreciate my answer, maybe give me a Like.
“Music acts like a magic key, to which the most tightly closed heart opens.”– Maria von Trapp

Hello Eni,

I cannot reproduce this in a reasonable timeframe on the release radar
playlist. So here is a way to reproduce, not quite the same but a very
related issue, in a user created playlist. Note that this issue is not
limited to MacOS only. I was able to reproduce it on MacOS, Windows and

Take two devices, A (e.g. Windows) and B (MacOS).
Create a playlist with 2(!) arbitrary songs, with any device.
Visit this playlist on device A and B.
Cut internet access from B.
On device A: replace the second song in the playlist with a different one
(remove, then insert again).
Play the first song locally on device A
Connect to the internet with device B. (the playlist will not update)
On device A(!) select to play from device B.
Skip one song on device A
(see that the old second song is now playing)

Additional notes:
* When selecting the new song, directly on device A, an error is
encountered. I am guessing that the song is being (not sufficiently)
uniquely identified by some song specific metadata. But the index is not
respected. As when repeating the experiment with the same songs but swapped
places, an explicit request to play a song on another device causes the
correct song in the wrong place (without a playlist update) to be played.
* I mentioned that this way to reproduce is not exactly the same as the
original issue. As when I encountered it initially, I explicitly selected a
song in discover weekly (not with skipping), which caused the old song at
that index (!) to be played.
* From my observations, android and MacOS have similar behavior. Windows is
even more broken. On Windows (as device B now) it is possible to select to
play on this device (on device B), which triggers a reload of the playlist
on the other OS'. It is also possible to skip forwards and backwards on
Windows (as device B), which would also trigger a reload on the other two
devices. So it is significantly easier to reproduce on Windows, but still
occurs on all other OS'.
* Note that on MacOS, after some time (when looking at the playlist), an
unprompted refresh is performed (sometimes).
* Also: I didn't test every combination on every device.

The video:

Regarding your Question: *We'd also like to know if this happens only when
using the Connect feature and if it happens on any device.*
Yes I am talking about the connect feature, what other features are
there to test?

Hey @maximilianmairinger,


Thanks for the detailed description of this issue.


We've forwarded this to the relevant team here at Spotify, however, we can't confirm when it will be addressed. In the meantime, please make sure to keep your app up-to-date.


Help others find this answer and click "Accept as Solution".
If you appreciate an answer, maybe give it a Like.
Are you new to the Community? Take a moment to introduce yourself!

Suggested posts