1Password extension doesn't fill in properly with no username field
Comments
-
Thanks for the update, @jmreekes. Just to be clear, you're using the latest 5.3 beta?
0 -
I am. I'm using 503002
0 -
Cool, thanks. I'll get it filed.
0 -
The issue is present in beta 503003 as well
0 -
Thanks @jmreekes .
0 -
Hi @jmreekes,
The good news is that I got that verification page with the password field only. The bad news is that I can't make the extension fill nor can I get the error.
Just to be clear, you're not getting any errors, just that it doesn't fill the password, right?
I've saved the page, so we can do the testing locally.
0 -
Great, thanks!
0 -
The new betas are using a new version of our filling algorithm. If you're using the current shipping version of 1Password for Mac that may explain the discrepancy. Thanks for getting back to us.
0 -
Hi @jmreekes,
I believe I know what the problem is and it is what we're already investigating for a while now, it has to do with some of our filling libraries being compiled for 64-bit only and your iPhone 5 is a 32-bit CPU, that's why I can't reproduce it on my iPhone 5S running the 64-bit CPU.
We'll get this fixed to work on 32-bit devices as well.
0 -
Great.
0 -
Keep an eye out on this in the changelog, we will try to mention the 32-bit support for the filling system. I'll also update this thread as soon as I have more information to share.
0 -
-
Hi @jmreekes,
That's great news. I didn't see anything about the fix and when I saw your post, I asked Rad, and he said it should definitely be fixed in the latest beta.
So, there you go, the fix made it but we didn't include it in the changelog.
Awesome! Thanks for being patient with us as we worked to fix this.
0 -
Yep, it definitely was a pesky one. Now, on to the next pesky critter. :smile:
0