Exact match and close match... is it gone from 1Password 8?

Hey yeah so we have a team of a dozen or so staff, and we have many customers that all have different subdomains, so some logins my be saved as customer1.service.com, generic addresses such as admin.service.com, etc. With 1P7 it would show the exact match, then 'close matches', which is what we would end up using 99% of the time.

The other example is not with customer subdomains, but with vendors that may have a dozen different login addresses. Eg some Ingram Micro logins are for au.ingrammicro.com/Site/home, some ingrammicro.com.au, some ingrammicro.com/login, etc.

Now that 1P8 matches on exact URL, we've got 837 logins that we would have to review and correct, then all of our internal bookmarks and procedure documents to update to use those exact addresses that are in 1Password.

We tried to use 8for half a day, but it really slowed down most aspects of the business, so we rolled all systems back to 1P7 and did an EDM to all business customers to not upgrade.

I also found that with my personal account on Android and iOS it keeps signing me out of one account (as I am signed in with both my work and personal 1P accounts), and on desktop I simply could not get both accounts to work. I could get them signed in, but then the Chrome extension would only ever show results from the account I signed in with first.

From what I can find online, eg on Reddit etc, there are literally thousands of people having these problems and sticking with 1P7. Not to mention that 8 seems much slower and laggier in the UI. This is often the case when using a bloated underlying framework such as Electron. Teams, Discord and a few other apps also have the same 'feel', hence I deleted my Discord account and use Teams Web instead.

I hope that feedback helps, as we otherwise like the product, and chose it specifically due to Troy Hunt's integrations.