beemdevelopment
Unable to manually reorder after removing groups
Version
3.4.1
Source
Google Play
Vault encryption
Yes (with biometric unlock)
Device
Oneplus 7T
Android version
14
ROM
No response
Steps to reproduce
Long press entry No move option or ability to change order
What do you expect to happen?
Be able to change the order in Custom sort mode.
This was supposedly locked out if you had groups enabled, but even if you delete all groups the sorting ability doesn't return.
What happens instead?
Only the other options are available
Log
No response
Ah you can disregard my comment in #1418. It seems like you're running into a bug because this should definitely be possible still. Could you send us a screenshot or perhaps even a screen recording of what you're trying to achieve? Please make sure there's no sensitive information in it.
Unless you are in a rare corrupt state you should be able to re-order entries when no groups are selected and your sorting is set to custom.
Well, the screen recording wouldn't be helpful since it won't show me trying to drag the entry.
No way to move the entry. I can only select it and make changes using the upper menu
Well, the screen recording wouldn't be helpful since it won't show me trying to drag the entry.
Believe it or not, it often gives us more context than you think.
Thank you for the screenshot though. I can't for the life of me seem to reproduce this and the only time we stop a user from dragging around an entry in this scenario is when the sorting is not set to 'Custom', a groupfilter is set or the searchfilter is enabled. If you're sure this is not the case then I advise you to play around with creating a new group, set the group filter to be that group and then untoggle it again. This should reset the groupfilters state (if that was the issue here to begin with) and you hopefully should be able to drag entries around again.
That seemed to fix it. It has been like this for months, so it seems that groupfilters state has been stuck all this time!
Ah happy to hear that that solved the issue for you! I will play around and try to see if I can reproduce this but it's entirely possible this is already fixed in the current version. Sorry for the inconvenience.