New Items appearing at top of list despite alphabetical sorting?

I'm finding in 1Password8 Beta for iOS/iPadOS and the macOS beta, that when I add a new login from Safari, at first it doesn't show up at all in my 1Password8 list of logins. I have to go to all items and then it shows at the very top. But when I go back to Logins, it then shows up but is at the very top, even though I have my sorting set to be alphabetically and not newest first. Is this a known bug? Just passing along feedback.


1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided

Comments

  • Hey, @volcom45. I'm not able to reproduce this behavior myself. Does this happen for every new item you save? Are the rest of your items sorted alphabetically?

  • volcom45
    volcom45
    Community Member

    Hi @rob yes, so far, the last 2 that I've created from inside of Safari on my Mac, have gone to the top of the list. Firefox is the last one. It's been a day and it still remains at the top even if I hard close the apps. But yes, the rest of the logins are sorted alphabetically by name with Firefox right at the the very top. It's bizarre. I keep trying to change the sorting to something else and then change it back yet Firefox still remains at the very top..

  • I'm befuddled. Is there any chance you could send a screenshot of what you're seeing with anything sensitive removed? Just to make sure I'm on the same page as you.

  • volcom45
    volcom45
    Community Member


  • volcom45
    volcom45
    Community Member

    @rob See what I mean? I added the Firefox login from 1Password for Safari, which maybe has nothing to do with the behavior, but I cannot for the life of me get Firefox to go to the F section alphabetically like everything else is sorted. It's always at the top on 1Password8 for Mac and the 8 iOS/iPadOS betas. Any ideas on how to force this to sort where it's supposed to go?

  • volcom45
    volcom45
    Community Member

    @rob I should also point out that ironically, when I open 1Password for Safari or the Safari extension on iPadOS/iOS, and click logins, Firefox is sorted correctly in the F’s. But in 1Password 8 for Windows, Mac, and the iOS/iPadOS 8 betas, all show Firefox at the very top in the main app. I even tried editing the name to include a different letter in front to see if it would then sort, but nope. Always remains at the very top, never moves anywhere. This is driving me crazy!

  • Jack.P_1P
    edited May 2022

    Hey @volcom45:

    This sounds a bit silly, but by chance is there a leading space on your Firefox Login item's name? " Firefox" instead of "Firefox"? The leading space isn't displayed in the list view, but adding a leading space will sort it to the number section as you're running into.

    Jack

  • volcom45
    volcom45
    Community Member

    @Jack.P_1P I wish there was but sadly there is not :(

  • volcom45
    volcom45
    Community Member

    FWIW, when I login to my.1password.com, it is sorted correctly and not at the top. Same with the 1Password for Safari on Mac and iOS/iPadOS. It is only in 1Password8 for Mac, Windows and iOS/iPadOS beta that it continues to stick to the top despite the order being set for alphabetical. I'd really like to see this get fixed.

  • Hi @volcom45:

    I completely understand. Just to make sure, is Firefox always at the top, no matter which sort option is used? If you change sorting to Date Created, and use the Oldest First order, does Firefox remain at the top? Let me know!

    Jack

  • volcom45
    volcom45
    Community Member
    edited May 2022

    Hi @Jack.P_1P , nope, it either remains at the very top or the very bottom. ;) If I change alphabetically sorted to reverse, it goes to the bottom. If I change it to Date Created and Oldest First, it goes to the very bottom. Thanks.

  • volcom45
    volcom45
    Community Member

    I decided to just delete the Firefox login completely and re-add it in the app from scratch. End result, it’s now down in the F section. Not sure what caused it to remain at the top still, but glad to have it corrected and hope that future additions don’t do the same. ;)

  • Weird... I'm glad you were able to resolve the issue, and thanks for this report regardless. We'll have to keep an eye out for anything similar happening again.

This discussion has been closed.