Cider since v3.1.0 completely unusable. Only working solution is by downgrading back to v2.6.1

[xPaiiN]

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 confirmed that no support FAQ resolves my issue.
• 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).

How did you download Cider?

Taproom

App Information

{"clientInfo":{"client":"dotnet","env":"production","arch":"AMD64","platform":"win32","platformFriendly":"Windows","build":"desktop","clientVersion":"310","capi":"81b56bad-d80e-4c84-944a-692e4e1a6cf7","subversion":"1"},"buildInfo":{"version":"3.1.9","commit":"486ebca9be76dd12360168f19f4143e0a5358a5b","branch":"main","buildDate":"1765233904979","changelogUrl":"3.1.0-release","codeName":"Gala"}}

Operating System

Windows

OS Version

Windows 11

How would you describe your issue?

Frontend

Commit Hash

486ebca9be76dd12360168f19f4143e0a5358a5b

Describe the Bug

The app fails to remember my Apple Music login credentials (logging in via Apple Music popup window) and won't load any of my playlists, let alone play any track. The Home, New and Radio sections do not load, and the search finds nothing at all. None of the v3.1.0+ versions work properly. I could only download v3.1.0 from taproom (thanks a lot for that), but updating in-app to v3.1.8 or v3.1.9 didn't fix anything.

I don't think Cider has ever been in a halfway usable spot, becuase there are always annoying bugs. But all users want is a music player for Apple Music. There has never even been a clear direction for how Cider should operate, but users don't care about design or plugins if they can't even use their (paid!) music app for listening to music.
I'm downgrading back to v2.6.1 because that seems to be the last stable version before v3 got released and the whole download section got messed up and integrated into taproom which is an absolute buggy chaos. At least with v2.6.1 I can finally listen to music again with the "temporary" fix (https://gist.github.com/cryptofyre/01325a9a3e9ecc76580afee755ee2cf6), but there are still annoying bugs in that old version.
For example, the most annoying bug is playlists not remembering their sorting and playing the wrong songs. When sorted by "playlist order" and "descending" and playing the first track at the top, it doesn't actually play that song. Instead, it plays from the bottom of the list, as if the sorting is reversed internally while displaying correctly visually. iirc the same bug has been prominent in v3, when it was working for a short time.

But I digress, please fix your sloppy app.

Steps to Reproduce

download and install cider v3.1.0, login and try to play music or load anything. even after updating to v3.1.8 or v.3.1.9 it is not fixed.
I've tried uninstalling and installing multiple times and even on a different computer because I thought somehow my windows installation was messed up but even on a clean install it has the same problems.

Anything else?

No response

[cryptofyre]

This seems like a more complicated and specific issue than you lead it to be as a generalization on the latest version.

I personally haven't encountered this throughout my testing, which begs a serious question about what's going on for you.

There are a variety of reasons why, and I really can't help without additional logging you'd need to provide via the console (CTRL+SHIFT+I)

My immediate assumption here is that you have a rogue DNS or server connection related issue to our services that is preventing you from fetching the latest assets required for playback.

We're hard at work delivering a complete MusicKit replacement via v4, however, this is still a very complicated work in the making, but that doesn't mean we left 3.1.9 in an unworkable state.

[xpbl]

Workaround: Use your media-user-token cookie as the Apple Music OAuth popup is completely borked for me too.

[xpbl]

Could be on Apple's end who knows but blaming Cider devs because you can't log in is an asshole move

[xpbl]

When v4 rolls around though I hope Cider devs address performance and reactivity bugs (#1312), most notably elevated RAM usage by ideally utilizing more native code on platforms other than Windows because Cider is among one of my top RAM consumers, right under my web browser or VSCode

USER         PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
bliss     144973  0.7  5.5 1459549348 871684 ?   Sl   15:04   2:05 /usr/share/code/code ...
bliss     151530  3.1  4.5 8701288 718824 ?      Sl   15:18   8:06 /usr/share/librewolf/librewolf ...
bliss       4617  3.1  3.8 13839488 606404 ?     Sl   Dec21  61:24 /usr/share/librewolf/librewolf
bliss      30899  1.1  3.7 1478185368 592684 ?   Sl   Dec21  18:54 /usr/share/code/code --type=zygote
bliss     135310 24.6  3.7 1459798188 586832 ?   Sl   14:54  68:26 /proc/self/exe ... # Cider subprocess
bliss     144710  1.1  3.4 1463028916 543176 ?   Sl   15:04   2:58 /proc/self/exe ... # Cider subprocess
bliss     201420  0.4  2.1 8252408 345916 ?      Sl   19:07   0:07 /usr/share/librewolf/librewolf ...
bliss     209725  3.0  2.0 3933448 328520 ?      Sl   19:26   0:10 /usr/share/librewolf/librewolf ...
bliss     154901  0.0  2.0 2354904 316728 ?      Sl   15:25   0:06 spectacle -r

[cryptofyre]

This very likely has to do with your system not having full GPU acceleration, we're pretty limited by what we can do in terms of native code as playback cannot exist outside of Chromium as DRM is not supported otherwise on Linux.

4.x does ditch MusicKit but that's half the battle.

[xpbl]

Ah that's right WebKitGTK is terrible

[cider-collective]

Hello again!

We've noticed that you haven't replied in a while. Unfortunately, our team isn't always able to address issues as quickly as we'd like. To help us assist you more efficiently, please provide the following information:

1. Ensure your client is as up-to-date as possible. You can do this by using the experimental release on Taproom (if available) and the PTB release through the in-app updater.
2. Let us know if the issue is still present. If it is, please provide the version you're using and mention any changes you've noticed since reporting the issue.

This information will help us identify whether the issue has already been resolved.

Please try to update us within the next 20 days; otherwise, we will close this issue.

Thanks for your help! 😃

[xpbl]

...