Playback stopping on some songs and messes up queue on resume

[quiellll]

Preflight Checklist

• I agree to follow the Code of Conduct that this project adheres to.
• I have searched the issue tracker for a bug report that matches the one I want to file, without success.
• I have checked that the correct behavior occurs on Apple Music Web (if applicable).
• I have verified that my issue is with a supported version and that it is with the desktop app (Support for other areas can be found in our Discord / on the appropriate repo).

Download Source

Itch

Operating System

Arch Linux

Commit Hash

No response

Connect Instance ID

No response

Build Timestamp

05/07/2024 @ 04:22:08 AM

Describe the Bug

Songs stop playing after a short period of time, approximately around the 1:00-2:00 mark in my case.
Hitting play restarts the song, and instead of continuing with the desired queue, it uses the history as a queue.

In my case, it used my history (with songs that I had played earlier on my phone) and used it as a queue instead of the rest of the songs of the album.

Also, if a song has gotten stuck, it will get stuck more times. The only way that I've found to avoid this issue is to manually click on a timestamp greater than the one where it stopped, so it loads the song data, and then starting it over.

Steps to Reproduce

1. Searched for an album.
2. Clicked on the album.
3. Started playing the album using the play button.
4. Song got stuck.
5. Hit play again.
6. Song restarted.
7. Check queue to see it changed.

Anything else?

I think the album I was listening to does not have much to do with this issue, since i tried with another song and it happened again. Restarted Cider and my computer and it happened a few more times, and it has seemingly stopped happening (for now). Will try to keep updated and help as much as I can

[github-actions]

Hello @quiellll 👋

We really appreciate you taking the time to report this issue, please double check your issue to make sure you are clear and concise in your description. This will help us to help you as quickly as possible.

We'd like to ask you be patient and we will get back to you as soon as we can.

In the meantime, take a look at our FAQs which may answer your question.

Thanks again and we hope you enjoy the app! 😃

[Hezkore]

I have a similar issue, where the play button acts very weird and some songs stops about a second or so into the song.
Sometimes the play button either doesn't do anything, or it plays a song from the history.

In the video below, the song "Frozen Light" stops after about a second.
And "Meeting the Master" never even starts, and clicking Play does nothing, until it eventually plays a song from the history.

play_acting_weird.mp4

[quiellll]

Yes!
I also forgot to add that. Sometimes, when it gets stuck, the play button gets its own life or something and toggles whenever i move the mouse, hover over anything, or click on another button (such as the queue one).

I've been using cider only for less than a week, but I had no problems on the previous release, before updating to the last version :(

[GGBond69]

have met the same issue too.after the song stopped,there is no react when clicking the play button.
And the playlist would be replaced by history songs:the order is inverted.

[stewartkyle]

I am having a very similar issue on Windows 11 using the latest build from the Microsoft Store (2.4.0_1). I open Cider, click to shuffle my library from the Songs page, and one of the following happens:

1. A song shows up as currently playing, but does not actually begin playing and is paused at 0:00. Pressing Play causes this song to be removed from currently playing and Cider then plays the most recent song from my history instead. My history is then used to populate the queue in reverse order.
2. Cider plays the first song normally. Eventually, when switching to the next song (sometimes it happens immediately on the second song, but sometimes it happens later in the queue), the song does not begin playing and the behaviour described in point 1 above happens.

Checking the console for errors, I have seen this error when the next song fails to start playing:

GET <iTunes URL ending in .mp4> net::ERR_HTTP2_PROTOCOL_ERROR

and these errors when Cider uses my history to populate the queue as described above:

Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'inLibrary')

Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'attributes')

Uncaught (in promise) Error: The play() method was called without a previous stop() or pause() call.

So, it seems like Cider is playing a song, encounters an error that prevents it from loading/playing the next song, and then generates an additional error when attempting to play() again because it was not actually told to stop playing the previous song.

I have tried clearing my Cider cache repeatedly as well as tweaking the settings with no luck.

This issue was not present on 2.3.x.