troubles logging in to PayPal

oconbach

I am having trouble logging in to PayPal on my iPhone. I had hoped password would appear automatically. It appears that is not the case. Checked in your support forum and there is some type of cut and paste option. I tried that and PayPal would still not accept the pasted password. I can type it manually and it works. There is something not seamless about 1password and finance apps (Paypal, B of A, Vanguard) etc that doesn't seem to work. What am I missing? (btw: On one month trial and if I can't go back and forth from browser to apps with my most important financial sites I am not sure I am ahead in the game)

---

1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided
Sync Type: Not Provided
Referrer: forum-search:Can't login in to paypal app om iphone

Corey_C

Hi there @oconbach :)
Sorry for the troubles you have been having. When it comes to iOS apps, AgileBits provides a way for developers to integrate 1Password into their apps so people can use it directly. However, while AgileBits provides the method, it is still something that the individual app developers have to implement themselves and many apps have not done so. A list of apps that have added built-in support can be found here:

Apps ❤ 1Password

For the apps that haven't added integration, the only option that remains is opening 1Password, copying the password you need, switching to the other app and pasting it there. It's not ideal, I know, but there's nothing that can be done as each app runs in it's own sandboxed environment. You say that copy-pasting isn't working while manual entry does? The only reason I could find for that is that the password in your 1Password entry is somehow incorrect. If you open up 1Password, go to your PayPal entry, tap on the password and click "reveal", it should show you what the stored password is. Make sure that the stored password is the right one.

Hope that helps. If it doesn't let me know. :)

AGAlumB

@oconbach: Indeed. Sorry for the confusion! While we offer a 1Password extension for iOS (which also works in Safari), it isn't something we can build into other apps ourselves. Their developers will need to add support for it. Otherwise it is necessary to copy and paste.

However, we have a website devoted to the 1Password extension for developers, so be sure to let them know you'd like them to add support for it and point them in our direction. We're always happy to help them join the ranks of apps that support the 1Password iOS extension!

oconbach

I found the problem with cut and paste. When I changed the PayPal password Safari jumped in with its suggestion. I was uncertain how all this was going to work so overtyped with my own password. Unhiding the password in 1Pass I find that it grabbed the Safari suggested password and NOT the one I over typed and that PayPal is now using. This explains why the cut and paste was not working but raises more questions about how 1Pass interacts with the browser suggested passwords.

Corey_C

Hi @oconbach :)
Good to hear you figured out the issue. The general answer to how 1Password interacts with browser suggested passwords, at least in my experience as a user, is not very well. That is why it is generally recommended to turn off password suggestion and password management from browsers entirely if you are going to use 1Password as they will usually only conflict with each other. An AgileBits team member may have better information on that but, as a user, that is my suggestion.

Although, if you are using Safari to sign in to PayPal, you could use the 1Password extension for iOS that brenty mentioned which will make things far easier and faster than the copy-paste method. Copy-pasting is only necessary for the times that the extension does not work.

AGAlumB

@oconbach: Ah, that makes sense. Unfortunately 1Password can't (and arguably shouldn't) try to fight with the browser itself to override this. We always recommend disabling browser "autofill" features (can also be done on iOS in Settings > Safari > Autofill) like this to avoid just this kind of conflict, rather than getting into a war with browser vendors which cannot be won. :lol: