Search fails with "General transient error" #89
Comments
|
Hm, I also got this earlier today. And now I'm getting: Not sure if it's related or not. |
|
Can't play anything today! Getting same kind of errors |
|
https://twitter.com/SpotifyStatus/status/694855504930148352
So the specific problems we see today are probably nothing to do with mopidy-spotify. |
|
Thanks @kingosticks |
|
Wonder if we should catch these though and make it a warning or error log entry and then have a debug entry for the traceback? Though these might be hard to reproduce, so maybe better just to leave the traceback and just make sure to have a better error message? |
|
@timothylhuillier but your exception should be handled. |
|
And Spotify is working again for me now. See if you are still having issues @timothylhuillier |
|
I confirm, I have already this problem when I looking for artist but when I go to playlist : http://screencloud.net/v/wQFh in bottom, my spotify music start. I develop my frontend app for sync my light so, I cancel and start mopidy every time. Before already oki but Since this morning I must reboot my computer that my search work. I don't know why edit : Now, I reboot my computer and I have already the bug |
|
Affected as well since today. |
|
Seems like there still are some issues, but Spotify doesn't report any issues on their twitter now. |
|
It seems you are able to do a search right after mopidy starts and after that it breaks. Weird. |
|
Historically I don't think 'Transient' errors are something they ever report since they don't affect all users. |
|
The strange thing is if you continue to retry the search, eventually a result will come back. This usually completes within 10 tries. |
|
I don't modifed anything but now, it's rework ... lol Edit : And not, I restart mopidy and I have again the problem... |
|
I've been watching this thread for a few days, but didn't want to weigh in if I had nothing useful to say. This issue only really appears to have impacted Spotify search; generally browsing for specific albums and artists seems to be working fine. The workaround at my office, has been to use browser history to find our favourites to add music to our play queue (our mopidy web client embeds the Spotify URI in to the URL (/#albums/spotify:album:44Ig8dzqOkvkGDzaUof9lK/Led%20Zeppelin/Led%20Zeppelin%20IV) as you browse, so we haven't been badly impacted. One final note: The issue has gone from intermittent to continuous over the last 24 hours for me. I'm not sure if I can do anything to help here as I know too little Python and have no experience with Spotify's APIs. If you need anything (even if it's just moral support!) please let me know. |
trygveaa
changed the title
|
This is indeed affecting numerous people today, possibly everyone. I've asked Spotify for information but they have not responded. Note that the search at play.spotify.com is working fine so this issue is probably confined to whatever Spotify service endpoint libspotify searches use; there probably isn't anything we can do other than handle the exception better. |
|
Still receiving this error today. |
|
https://developer.spotify.com/web-api/migration-guide/ - so it turns out Spotify turned off their old metadata API, which it turns out libspotify used... So this is basically going to be broken until someone scrambles to get a workaround using the web apis in place :/ |
|
The only client I currently have that works with this is mopify... mopidy springs the same error, but the results show up regardless. |
|
For the record, the reason mopify still works is that it doesn't use mopidy for search or metadata lookup. It just uses the new web apis directly from your browser. |
Spotify has discontinued their Metadata API, which libspotify uses. This means that search in libspotify, and thus pyspotify is not working. This changes the search to use the new Web API which is supported. This is a first step for fixing search, and makes it work again. We probably want to further improve this, and possibly move calling the API into pyspotify. Note that some parts of the Web API require OAuth (i.e. different auth than libspotify requires), but luckily search doesn't require any auth. The search results from the Web API misses some data compared to what libspotify does. The fields that are missing is bitrate and date from tracks, and artists and date from albums. It is possible to additional requests to get the artists and release date for albums, but this is left for a later improvement. Fixes mopidy#89.
Spotify has discontinued their Metadata API, which libspotify uses. This means that search in libspotify, and thus pyspotify is not working. This changes the search to use the new Web API which is supported. This is a first step for fixing search, and makes it work again. We probably want to further improve this, and possibly move calling the API into pyspotify. Note that some parts of the Web API require OAuth (i.e. different auth than libspotify requires), but luckily search doesn't require any auth. The search results from the Web API misses some data compared to what libspotify does. The fields that are missing is bitrate and date from tracks, and artists and date from albums. It is possible to additional requests to get the artists and release date for albums, but this is left for a later improvement. Fixes mopidy#89.
|
Fixed in release-2.3 branch by using the Web API for search. Will be released soon. Leaving the issue open until the fix has landed in the develop branch. |
|
Fixed in Mopidy-Spotify 2.3.1 which has just been released. Thanks to @trygveaa for making Mopidy-Spotify use the Spotify Web API for searching. |
|
Very good work with the fix. I was just wondering if the update is added to homebrew? I am still stuck with version 2.2.0. Maybe I am doing something wrong? |
|
Mine is |
|
Works like a charm. Thanks! |
|
I had to do a |
Sometimes when I start mopidy since today, I have this error :
And when I exit mopidy (^C) and restart more times, that oki. I don't understand why
Thanks
The text was updated successfully, but these errors were encountered: