You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm currently struggling to get my Navidrome (Subsonic) server running with this amazing app!
One of my issues was, that I received a HTTP Error 402 response too large error when using the Test Server feature.
After some debugging I stumbled over the SubMusicTestView class. It seems that it uses the first playlist with songs in it. If it happens that the first playlist has too many songs in it, it will throw this error.
In my case (Navidrome) the first JSON entry from the playlist fetch response had 100 songs in it. As Navidrome sorts the items ascending by name, I just had to create a new playlist with a name ordered above that playlist and add a single song to it. This might be a workaround for someone out there.
However, this seemed just to be one brick in my solution to get the app running. Might open a separate issue for that.
The text was updated successfully, but these errors were encountered:
This correct. Based purely on the number of songs, one cannot determine whether the playlist will be too large for memory or not. There are two factors to this:
the available memory is dynamic and cannot be known.
the response size is dependent on the amount of metadata that is present for each of the songs.
A possible solution could be to just try the next playlist upon receiving a Response too large error. This is still no guarantee, as all playlists may be too large.
Also, I should note this is purely a Subsonic API issue, as all other APIs support paging for the responses.
I'm currently struggling to get my Navidrome (Subsonic) server running with this amazing app!
One of my issues was, that I received a HTTP Error 402 response too large error when using the Test Server feature.
After some debugging I stumbled over the SubMusicTestView class. It seems that it uses the first playlist with songs in it. If it happens that the first playlist has too many songs in it, it will throw this error.
In my case (Navidrome) the first JSON entry from the playlist fetch response had 100 songs in it. As Navidrome sorts the items ascending by name, I just had to create a new playlist with a name ordered above that playlist and add a single song to it. This might be a workaround for someone out there.
However, this seemed just to be one brick in my solution to get the app running. Might open a separate issue for that.
The text was updated successfully, but these errors were encountered: