[Bug] Spotify user.id broken with recent localStorage change

[mczerski]

when I click on the Playlists except my playlists that i have on my spotify account there are some other weird named playlists. They are only showed in spotmop, i can't see them in moped or in spotify web player so I assume this may be a potmop bug. They all are from user "null". and if i filter playlists i own (top right filter) they are not filtered.

[jaedb]

What version of Spotmop are you running? Have you authorized Spotify from Spotmop Settings?

[mczerski]

Version 2.10.0. the problem occurs when i am authorized. If i'm not, there is No problem.

[jaedb]

That sounds like it might be to do with the change in structure for storing of Spotify authentication details. Are you able to try Settings > Reset all settings?

[mczerski]

hmm, this behaviour is on the fresh install of mopidy (the whole system is
fresh - on raspberry pi 3), but I will try when i get home.

2016-09-26 10:23 GMT+02:00 James Barnsley [email protected]:

That sounds like it might be to do with the change in structure for
storing of Spotify authentication details. Are you able to try *Settings

Reset all settings*?

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#147 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACpMcKhrD0z-g6oVZGIUhf-N7gpzIsHRks5qt4D-gaJpZM4KF7bg
.

mgr inż. Marek Czerski
+48 696 842 686

[mczerski]

after resetting settings still the same. also removed /var/cache/mopidy/spotify/ and /var/lib/mopidy/spotify.

[jaedb]

I've managed to replicate the issue and have isolated it to the SettingsService.getSetting('spotifyuser.id') calls that need to changed to SettingsService.getSetting('spotify.user.id'). This is a consequence of the latest release.

A new release, addressing this issue will be deployed shortly.