Fails to login to sites that used to work
1Password used to be able to login to my credit card provider and now all it can do is apply the userid, the password field can only be filled out by hand, please advise.
Comments
-
I assume you're using 1P4 or 1P5. If that's the case please try re-creating and saving the login manually—which allows 1P to "re-learn" the relevant login page.
Stephen
0 -
Hello there,
I have a very similar problem after updating to 1P 5.3 today. UserID and PW are still provided by 1P, but the auto-login doesn't seem to work for some of my logins anymore. Didn't AgileBits do some "brain surgery" in the new version of 1Password? Seems like something went wrong!
0 -
Same here only with latest version, but I've only tried website logins (haven't tried credit cards yet since the update). Wow, do I really have to re-create my MANY website logins???? That would be HORRIBLE
0 -
I actually had to re-create, or rather re-copy&paste, some of my logins. But, of course, I had to check them all. Thanks, AgileBits, what a fun Tuesday night!
0 -
Hi @HomerJay,
I'm sorry that you had to re-create a few Logins after the update. 1Password did get a bit of a brain transplant that was designed to make filling more reliable, and our team did a lot of testing to ensure that the changes didn't break anything. If you let us know a bit more about the specific URLs that you needed to update, we'd be happy to investigate what went wrong.
As Stephen mentions above, the Save a New Login Manually steps are a great way to help 1Password re-learn the fields that it needs to fill, particularly in case the website itself has made some changes under the hood to how its logins are handled. We'd recommend this procedure over copying and pasting details into a new Login item.
Hi @ckp,
Please let us know the URLs that are misbehaving. As mentioned above, the changes to the extension shouldn't have broken anything that was working previously, and if something is going wonky, we'd love to know where so that we can fix it!
0 -
I tried recreating one of the logins using method "save a new login manually", but it ended up unable to auto submit still. Again, my logins were working in 5.1. Here is one of the basic login webpages that no longer auto submits on my Mac 10.10.2 with latest Safari and extension. If you fix this one, it may fix a bunch of them.
https://www.firsttechfed.com
I'd really like to know if it's possible to remove 5.3, reinstall 5.1, and restore my pre 5.3 vault if necessary. 5.1 worked much better for me.0 -
Ok, I trashed 5.3 and installed 5.1 again. Everything works now. Upgrade to 5.3 = Bad. Please fix it.
0 -
I can find related responses easily since all my relate discussions are together in one part of my login profile and I get emails too. I add comments to other posts that have the same problem so they know they are not the only one. And I'm hoping to see a solution, or at least an acknowledgment that there is a bug here. All I ever saw was a canned response "try recreating all your logins", but that never solved the issue and would be a nasty workaround as well. Also, in my own post, for some reason nobody from your team seemed to want to answer my question about whether or not it's safe to remove 5.3 and go back to 5.1. I wouldn't know if 5.3 changed some "data" that would be incompatible with 5.1. But nobody would answer this. So, I ended up taking a chance and doing just that. It worked fine and now my 1password on my Mac works better again like it did before 5.3. You guys needs to fix this bug. 5.3 on Mac is worse and 5.3 is supposed to be all about making Mac better. For now on, I am going to wait for quite a while before upgrading to a new version. I will check the posts for common major issues before trying it in the future. In any case, I will try to avoid posting in multiple threads, but would ask you to try answering the questions in my own thread.
0 -
Hi @ckp,
I understand your frustration when things aren't working quite as well as you'd like, and I can see why you would be tempted to post in multiple threads. However, as Stephen suggests, it does end up complicating matters. Ideally, we'd love to keep the conversation in one place as much as possible. It allows us to more efficiently get to the bottom of an issue, as well as advise users of a solution. And it saves our team from answering the same question in multiple places.
We are currently looking into this issue, as you heard from one of our filing gurus in your other post. Let's keep the conversation regarding the auto-submit issue going in that thread. :)
All I ever saw was a canned response "try recreating all your logins", but that never solved the issue and would be a nasty workaround as well.
I'm sorry that the suggestion to save a new Login didn't work in your situation. This is generally our first step in troubleshooting - it does fix the problem in a lot of situations, and, if it doesn't, it gives us a much better place to start (because it eliminates the variable of an old or incorrect Login) ... particularly in threads where we don't have much detail to begin with.
Also, in my own post, for some reason nobody from your team seemed to want to answer my question about whether or not it's safe to remove 5.3 and go back to 5.1.
Of course, rolling back to a previous version is one way to work around this, but generally, we'd prefer that you would keep the latest version installed and work with us to track down and resolve the issue.
In any case, I will try to avoid posting in multiple threads, but would ask you to try answering the questions in my own thread.
Thanks so much for helping us keep the conversation organized. I just want to point out that Stephen is not an employee of AgileBits, but a dedicated user who is helping out here on his own time. I apologize if you feel that we on the team are not giving proper attention to the issue that you're seeing, but Stephen is simply trying to help out, he doesn't always have all the answers.
0 -
@ckp—apologies, I did not intend to offend.
Stephen
0 -
no worries. i just want to see the issue figured out and resolved and i was not really seeing much from agile bits in terms of trying to figure it out. if they can't reproduce it, then i would hope they have some type of logging or diagnostics to get them the info they need to understand what is going on. for me, all i have to do is put 5.1 on my system and all is well, or upgrade to 5.3 and all is not well. if it works with the same extension on 5.1 and not on 5.3, the problem is likely inside the 5.3 code.
0 -
Hi @ckp,
Version 5.3 was a big one because we switched from one filling logic to a brand new one. No matter how much beta testing we do, there was always going to be a transition period once we released this new filling logic into everybody's hands. Given it is so different there is the possibility that some sites still need worked on from our end and that's what we will do. This isn't a quick or easy task just because we're trying to be compatible with every possible way a web developer may design a login page - it's a bit like herding cats. As long as you have a thread regarding a specific site we're on the right track for working this out.
0 -
Yeah, I totally understand that your QA team cannot possibly catch all issues. That's a given. But from what I have experienced on this issue, it appears to me that you need some tools and/or logging for your customers to run that may get you more information about issues. This is especially important for issues that you cannot reproduce. I'm sure you guys will figure this out eventually. For now, I must remain on 5.1, since the auto submit seems to work for me.
0 -
Hopefully somewhere down the line then you'll find either an improved filling logic or extension that we release means you can run the latest version once again :smile:
0 -
I found your problem. The Safari setting to autofill username and password causes your 5.3 app to fail. 5.1 does not have a problem with this Safari settings being enabled. I would prefer to have the setting enabled for various reasons. Hope you can fix it to work like it did in 5.1.
0 -
Thanks @ckp! I see that you've been getting help for this issue in this other thread and that we started working with you via email in order to look further into the problem. We'll keep the conversation going directly via email so we don't duplicate efforts or cause confusion between here and there.
If you need help with a different problem, please feel free to start a new topic. Thanks! :)
ref: QIN-83779-879
0
