Google Multi-page login broken on iOS?
Since the 1Password 7.2 update and including the current 7.2.1 update on iOS 12 and 12.0.1, logging into Google has been a bit annoying since its login page is split across multiple pages with the username input on the first page and password input on a subsequent page.
The problem I'm having is that one the username page, using either the iOS Safari Extension or enabling the Autofill, I choose an Username/Password pair to use, the username is filled in and I go to password page where I expect the matching password to be filled in. Currently, I need to re-unlock the password vault and find the Username/Password I'm using all over again.
Either something about the new app update, iOS 12, or the Google login page is breaking the previously smooth experience and I hope you guys can find a way to fix it!
The Username/Password entry was made in the iOS App.
1Password Version: 7.2.1
Extension Version: Not Provided
OS Version: iOS 12.0.1
Sync Type: Dropbox
Comments
-
I had noticed this myself as well. I'll mention it to the development team to investigate if there are any improvements we can make on our end for this. Thanks for the report.
Ben
ref: apple-2370
0 -
Could you please try using the 1Password Safari extension on iOS to save a new login for your Google account, and then see if that'll fill as expected? In my testing here that worked.
Ben
0 -
Interesting. Creating a new login with the extension seems to work, directly typing in the 1Password app didn't. Hopefully you guys can work out how to automatically fix the all logins that are already created since remaking everyone is rather tedious.
By the way, it appear when signing into outlook.com the Safari extension didn't even fill in the email, another issue worth looking into.
0 -
It's not something we can reasonably "fix" for existing logins: We're not going to have 1Password modify user data. I'm glad that saving a new login based on the current form of the login page helps though. Cheers! :)
0 -
It wouldn't really be modifying user data as there is no change of the username or password. I presume what broke is whatever template for logins the 1Password app was using to identify which input on the page to fill became invalid and needs updating, which would at least fix new logins. I think a reasonable feature request would be to provide a way to update existing records so that username/passwords get put in the right spot.
0 -
We grab those fields directly from the page at the time we save the login item. Ideally it would be easier to update a record to fill in a newly updated form (which is what happened here) without having to save an entirely new item. That is something the team that works on saving and filling has been looking into. :+1:
Ben
0 -
Sounds good. Is this something that can be expected in the near future? Also, do you think you guys will have fix out for new logins created in app (if that's still broken for Google and Outlook? Haven't tried recently) vs recorded while logging in?
0 -
Also, I was curious if the issue was mainly Google changing it's page (thus the issue is reproducible in older versions of the 1Password app) which just happened to coincide with the launch of the new 1Password version or was there also a change of the 1Password end that affected things.
0 -
Sounds good. Is this something that can be expected in the near future?
That’s a rather big project, so probably not the very near future. I’m hoping the Google issue can be fixed in the shorter term, and I’m pushing for that, but I couldn’t make any promises at this point.
Also, do you think you guys will have fix out for new logins created in app (if that's still broken for Google and Outlook? Haven't tried recently) vs recorded while logging in?
Fingers crossed. :)
Also, I was curious if the issue was mainly Google changing it's page (thus the issue is reproducible in older versions of the 1Password app) which just happened to coincide with the launch of the new 1Password version or was there also a change of the 1Password end that affected things.
My understanding is that the issue is entirely that Google updated their page, which does happen with various websites from time to time. I don’t expect that any version of 1Password would behave differently. Most of the time this is easily fixed by saving a new login item and it is no big deal. The difficulty here, and why I’m pushing for additional measures, is that having a Google account is pretty ubiquitous. I’d rather not have to tell every customer to try saving a new Google login. Additionally many customers, myself included, have a multitude of Google accounts, so saving a new login for each one of them could be somewhat burdensome.
Ben
0
