Local Files aren't sorted properly

[mzmonkey]

Preflight Checklist

• [x] I agree to follow the Code of Conduct that this project adheres to.
• [x] I have searched the issue tracker for a bug report that matches the one I want to file, without success.
• [x] I have confirmed that no support FAQ resolves my issue.
• [x] I have checked that the correct behavior occurs on Apple Music Web (if applicable).
• [x] 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?

itch.io

App Information

{"clientInfo":{"client":"dotnet","env":"production","arch":"AMD64","platform":"win32","platformFriendly":"Windows","build":"desktop","clientVersion":"310","capi":"84e1275d-9945-4b82-887e-321708c616a5","subversion":"1"},"buildInfo":{"version":"3.1.5","commit":"53b47bd4a8d9e643b9d68fc840bd43f142dc1cca","branch":"main","buildDate":"1758927080767","changelogUrl":"3.1.0-release","codeName":"Gala"}}

Operating System

Windows

OS Version

Windows 10 22H2 Build 19045.6396

How would you describe your issue?

Frontend

Commit Hash

53b47bd4a8d9e643b9d68fc840bd43f142dc1cca

Describe the Bug

Local Files uploaded and added into an Apple Music Playlist appear at their correct position when using the "Playlist Order" sorting option but drop down to the bottom of the playlist when a different sorting option is used (See screenshot).

Descending Playlist Order:

Ascending Playlist Order (default):

Notice the 3 local songs that don't get carried over when sorting using a non-default sorting.

Steps to Reproduce

1. Upload a local song using the apple music web client or app
2. Add that local song to a user playlist
3. Use a sort option that isnt the default (For me it is specifically "Playlist Order: Descending")
4. Observe the song being stuck at the bottom of the page

Anything else?

Simply using what the apple music API provides and reversing the order without any post processing should be enough, though i'm not sure how realistic that is. I'm not sure what else is causing this because cider isn't open-source.

[cider-collective[bot]]

Hello @mzmonkey 👋

We really appreciate you taking the time to report this issue! Please double-check your report to ensure your description is clear and concise—this will help us assist you as quickly as possible.

We kindly ask for your patience, and we'll get back to you as soon as we can.

In the meantime, feel free to check out our FAQs, which may have the answer to your question.

Thanks again, and we hope you enjoy the app! 😃

[cider-collective[bot]]

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! :smiley:

[mzmonkey]

The Bug was originally reported on Stable version 3.1.5. The Issue still persists on the current PTB version 3.1.6 (PTB 200).

[cider-collective[bot]]

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! :smiley:

[mzmonkey]

Still applies to the newest stable release 3.1.7.

[cider-collective[bot]]

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! :smiley:

[mzmonkey]

Issue still present...

[cider-collective[bot]]

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! :smiley:

[mzmonkey]

This issue hasn't been fixed for 2 months and hasn't been mentioned in a changelog, so why do I have to keep track of if the devs fixed it or not?

#Please add the issue to a backlog. I don't want to reopen a stale issue just because i have better things to do than respond to a bot every 2 weeks!