Queue synchronization not working. Again.

Hi ​@jirikovoego! Thanks for reaching out!

Sorry to hear you’re having trouble.

Please try the following steps to help us figure out what's going on.

1. Make sure your iPhone and computer are using the same account and that the app is updated on both.
2. Double-check that both devices are connected to the internet—syncing won’t work without it.
3. Try logging out and back in on both devices to refresh the connection.

If it’s still not working, please let us know what app versions you're using and if this happens with all songs or just certain ones. 

Hi ​@Leonídia.Deezer, the feature started worked again itself at the moment. But it’s very unreliable :(

So, I was spending whole day with Deezer Desktop App yesterday at work. Later, then I left my workplace I wanted continue with Deezer on my iPhone. And what do you think? Yes, queue was empty again.😟

Another day. Leaving desktop app after whole work, lunch mobile one and queue is gone.

Another day, the same issue. Hey ​@Leonídia.Deezer, can an engineer check this?

Hi ​@jirikovoego In order to provide all the necessary information to our devs. Could you please let me know the steps you are following in order to test on our side? (i.e: Do you launch the mobile app, before closing the computer at work?, etc).
Thanks

Hi ​@Jaime.Deezer, it’s my suspicion that the issue is connected with using desktop/web app during the day and changing the playlist/songs/flows.

After that, when I open the iOS app I see empty queue, or queue stuck at something I played few hours ago.

I tried turn off/turn on the desktop app (queue in desktop app is ok everytime), continue playing in the desktop, but the iOS is still stucked.

Only solution in start playing in the mobile, desktop queue is changing immediately after that. Then everything starts working again. For a while.

Another day with the same issue. Sync between desktop and web app works. Not between Desktop and Mobile.

Hi ​@jirikovoego! I’ve reported this issue to our developers, and they’ve mentioned that the technical migration updates are expected to be fully rolled out by the end of Q1.

Once those updates are complete, this bug might be resolved as part of the changes.