I just tried out the new beta of 7.2 for iOS with autofill, and this feature is in many cases just amazing!
There is one specific use case where it is entirely unusable though, and that is if I have several different logins with the same login name on different subdomains.
For example, if I have two different subdomains that is server.domain.com and git.domain.com and my login name is the same for those ("user"), but the password is different, and then I use autofill for any of those, this happens:
I first get a suggested login, but it seems to be any random login from any subdomain to domain.com, and not for where I actually try to log in.
So, I click the key icon instead to list all logins for the current site, and these are the options I find in the list:
So, in other words, there is nothing that differentiates those logins at all in the list, so I will have to guess or open the 1Password-menu instead (where it is not clear which login belongs to the current subdomain either, but at least better in most cases).
For some domains I have probably over 20 different logins for different subdomains but with the same username in this way, and it is a mess to handle that in the normal 1Password login list, but practically unusable with autofill.
In my view, this problem is easily solved (if Apples API allows it of course) by making it possible to only list logins for the specific subdomain I'm on.
I already missed that feature far more than anything else in the iOS version of 1Password, but the behaviour in autofill makes this feature even more needed than before.
It would be truly amazing if you would fix this issue and make autofill (and the rest of 1Password on iOS) become as good as it could be.
1Password Version: 7.2 (70200001)
Extension Version: Not Provided
OS Version: iOS 12 DP9
Sync Type: Not Provided