Default Chapter Sort is not functioning properly
Pheonix-Flames opened this issue · comments
Steps to reproduce
- Open the app on your device.
- Navigate to More > Settings > General > Default Chapter Sort.
- Set the Default Chapter Sort to descending order.
- Open a new novel from any source within the app.
- Notice that despite the Default Chapter Sort being set to descending order, the chapters are sorted in ascending order by default.
- Attempt to refresh the novel by swiping down on the screen.
- Verify that even after refreshing, the novel's chapters remain sorted in ascending order.
- Check the sorting option to confirm that the Default Chapter Sort is still set to descending order.
- Manually change the displayed sorting order to ascending and then back to descending.
- Observe that after this manual adjustment, the chapters are correctly sorted in descending order as per the Default Chapter Sort setting.
Expected behavior
If the Default Chapter Sort feature were functioning correctly, setting it to descending order should ensure that when a new novel is opened, the chapters are automatically sorted in descending order. Refreshing the novel should maintain this descending order, and checking the sorting option should confirm the selected setting. Users would not need to manually adjust the sorting order, as the default setting would be accurately reflected without any additional steps.
Actual behavior
Despite setting the Default Chapter Sort to descending order in 'More > Settings > General > Default Chapter Sort,' new novels are sorted in ascending order by default. Even after refreshing the novel or checking the sorting option, the default setting remains in descending order, yet the novels are displayed in ascending order. However, manually changing the displayed sorting order to ascending and then back to descending corrects the sorting, aligning the chapters in the desired descending order.
LNReader version
2.0.0
Android version
Android 11
Device
Realme 3 Pro
Other details
No response
Acknowledgements
- I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
- I have written a short but informative title.
- If this is an issue with a source, I should be opening an issue in the sources repository.
- I have updated the app to version 2.0.0.
- I will fill out all of the requested information in this form.
YouCut_20240503_133254410.mp4
Is it fixed ?