Open hooliowobbits opened 3 years ago
ah! it just started working
$ spotify seek 0
Position set to 0s
..what's going on there do you think?
possible that the API returned incomplete data - item
key had no value, so it was evaluated as None.get('duration_ms')
not sure why this would happen since when you try running spotify seek 0
with no song playing, it shows an error message (no playback session detected) instead of that traceback.
Hi mate, I may have closed this issue too early; this was happening again this morning.
I'll try to keep testing this to see what's going wrong, though I can't seem to replicate it on my end. What device are you playing spotify from?
well, i have several.. ;) but the ones exhibiting the issue are both 20.04 with the python dependencies locally installed using system python 3. It feels like an API issue. I wonder in that instance if there was anything in the API return? perhaps a verbose mode might help
Hmm I really can't seem to replicate the issue on my end, so I configured the cli to save the last response of every API request (excluding token refresh) to ~/.config/last-response.json
in v0.3.11. Hopefully this will help you with debugging.
The API must have returned something since some error handling is set up, but **the response might have been incomplete. Strange that this only happens sometimes.
I get this on two machines, both of which were working yesterday. A Spotify API change?