-
Notifications
You must be signed in to change notification settings - Fork 198
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
500 error on my playlists, causes client breakage #853
Comments
Thanks for the report. I believe that your playlist now contains at least one track (with ID 2295) which no longer exists in your library. This sort of thing is not supposed to happen as tracks are supposed to get removed from any playlists when they are removed from the library. But I guess that some unusual circumstances could still lead to this. When you view the playlist on the Music app web UI, do you see any entries with no proper name shown? It may be difficult to find out, what has caused the situation in the first place. But I should anyway add some sanity checks to the SubsonicController so that such stray tracks wouldn't break the playlist fetching. |
Okay, that probably explains it. If you remove that track 6 from the playlist (and any others like it), then it should fix your problem. I will anyway fix the Subsonic API implementation to be less fragile on such cases. But it will of course take some time before the fixed Music app release is available. |
I can confirm that removing the empty files from the playlist does fix the client. |
Also, set non-null values for some of the fields of the returned broken track as the Ultrasonic client doesn't seem to tolerate null values on all fields. refs #853
The fix for this problem has now been released in Music v1.2.0. |
I can confirm my client no longer fails! Thanks 😃 |
Hi,
My client (Ultrasonic on Android) experiences some breakage due to playlists returning some
NULL
files?... Here is the nextcloud log snippet from/usr/local/www/nextcloud/data/nextcloud.log
:The text was updated successfully, but these errors were encountered: