New early access update is now available

@James_Dressel_1P I hope that you continue to improve 1Password. Every software contains bugs. Some are minor, some are major and some are even blockers.
I'm working for more than 20 years as a software developer and none of the companies I've been working with would have considered releasing an application with a blocker issue like the badly broken search. Due to this issue the only remaining way to reliably find an item within hundreds of elements is browsing them! Sorry, but that is not the way the AgileBits I used to know handled serious issues.

@viswiz I think the best we can do here is promise that 1Password 8's first stable release certainly won't be it's last and ask for some patience as we continue to improve the product. We have a solid track record of frequent updates, and I imagine that'll be even better once all of our development efforts can focus on v8.

As we've discussed in other threads, there are downsides to having search pick up substrings the way you'd like for it to without first building a more solid foundation (i.e. it may break search entirely for some languages). We'd like to build that foundation eventually, but it won't be ready for the first stable release.

Ben

I've seen the messages about the search capabilities. It's true that it has some limitations right now. For instance, if you'd like to search for an entry named "AgileBits", typing "Bits" won't give you what you want, you have to start by typing "Agile". if the word is "Agile Bits" or "Agile-Bits" typing "Bits" will work however.

Basically, seems like 1Password 8 can't search for parts of words if they don't have spaces, dashes and so on.

For instance, if you'd like to search for an entry named "AgileBits", typing "Bits" won't give you what you want

This specific case would actually work as desired. If the entry were named "Agilebits" and you searched for "bits" the item would not be found, however.

Ben

@1P_Ben Thanks, indeed you're right. Uppercase works. Any insight on why "Agilebits" doesn't work?

I'm used to many popular password managers but mainly used 1Password and Keepass. KeepassXC (cross-platform third party client) can search pieces of words everywhere, uppercase of not, even those contained in URLs, notes etc.

That can be quite practical in some situations.

@1P_Ben I‘m using 1Password almost since its first release. Search always worked as expected… it just found what I was looking for ignoring the case or if it’s just a substring. This is the way search typically works in Spotlight, Word, google or any other application. It‘s even the way it still works in 1Password 7. Even taking into account that version 8 is not just a rewrite but a completely new software who thought it‘s a good a idea to implement a sub standard search?

In the other thread you mentioned Unicode problems and that it takes time to resolve. This thread is two months old and nothing has changed.

I agree that AgileBits had a solid track record of frequent updates. But your company has changed significantly. The old AgileBits would have released the new sharing feature with accompanying security whitepapers. Not this time…
In the past you would not have called a version ready for release with major problems still being unresolved.

No offense, but having a barely functioning search capability is a major issue. I understand needing to develop a solid foundation to implement more advanced search functions, but if that foundation isn't ready yet, 1Password 8 shouldn't be released until it is. As @viswiz, when you have 100's of passwords, a fully functioning search feature isn't a luxury, but a necessity.

+1 on need for global search to work like it does in v7.

@MacKopes

Could you please clarify what you mean by "global search"? I'd like to be sure we're talking about a known situation and not something new/unknown.

Thanks!

Ben

@"J.M"

Any insight on why "Agilebits" doesn't work?

Frankly it is a bit above my head but one of the resources I was pointed to for reference was

All sorts of things you can get wrong in Unicode, and why

Ben