Getting started with 1Password for your growing team, or refining your setup? Our Secured Success quickstart guide is for you.
Forum Discussion
gmpalter
2 years agoNew Contributor
Passkey crashes PayPal app
I managed to create a passkey in the PayPal app on iOS. (Trying in Safari on both macOS and iOS said that the browser wasn't supported.)
When I try to login to the PayPal app using my passkey, the app crashes.
BTW, when I saved the passkey, 1Password changed the name of my login item from "PayPal" to "paypal.com". Is this intentional?
Also, I had 1Password open to the login item when I created the passkey. When I went back to 1Password, it didn't show the passkey in the item. I had to select another item and come back to see that it was there. (My other devices showed the passkey immediately.)
1Password Version: 8.10.16
Extension Version: Not Provided
OS Version: iOS 17.0.1
Browser: Not Provided
28 Replies
- 1P_Dave
Moderator
I'm happy that you're not running into the original issue anymore. ๐
Correction: I still get the Sign in via Passkey after the login via FaceID, Password, 2FA, FaceID shenanigans where I just can hit the x button as Iโm already authenticated. I also tried logging out and using Passkey to log in. But the next time it just starts again.
I'm seeing the same thing when using the PayPal app on my own iPhone. This is indeed something that PayPal would need to take a look at and I recommend reporting it to their team: PayPal Contact Us
-Dave
- DamnatusDedicated Contributor
Correction: I still get the Sign in via Passkey after the login via FaceID, Password, 2FA, FaceID shenanigans where I just can hit the x button as Iโm already authenticated. I also tried logging out and using Passkey to log in. But the next time it just starts again. Pretty sure, 1P cannot do anything there. So this is primarily just for the sake of completeness.
- DamnatusDedicated Contributor
1P_Dave tested and it seems to work here. Thanks for the notification! Got into the PayPal app and tapped on passkey, then got 1Password slide up from the bottom with the current used PayPal login mail asking to save passkey, then got to a selection view for all PayPal items in my vault (with the option to create a complete new login item also). The matching existing PayPal login (same email) was preselected and after confirming it was stored like it should. No app crashes or anything (also nothing logged in Analytics Data).
PayPalโs App still is overall clunky when signing in with FaceID enabled mail/password, then 2 FA, then again FaceID and the first time after saving the Passkey also showing the prompt to use the Passkey for login (or it may be activated by the iOS Passkey API). But after the second login, the Passkey prompt is not shown again after the other steps (FaceID, login, 2FA, FaceID).
- 1P_Dave
Moderator
gmpalter, @chrisminett, Damnatus, @SchmidSP, timl23, @joegurt, 1proller, @Flawless, michaelyork
iOS 17.2 was just released by Apple and it includes a fix for the issue where saving and signing in with passkeys using 1Password in iOS apps didn't work. You can find instructions on how to update here:
If you're still having trouble after updating to iOS 17.2 then please let me know. ๐
-Dave
- 1P_Dave
Moderator
Thanks for the question. That would be a behaviour that PayPal would have decided to include as part of their implementation of passkeys and isn't something that 1Password can control.
Passkeys are very early days and different websites will provide different experiences. As passkeys mature and become more ubiquitous over the coming years the experience will become more polished and standardized across the industry.
-Dave
- gmpalterNew Contributor
Any thoughts on PayPal's website's behavior asking for a TOTP code when I use a passkey to login?
- 1P_Dave
Moderator
Thank you michaelyork. ๐
-Dave
- michaelyorkFrequent Contributor
Happy to report the fix is once again present in iOS 17.2 Beta 1.
- 1P_Dave
Moderator
Thank you for the reports, iOS 17.1 indeed does not resolve the issue. I'll keep an eye out to see when a fix does appear in a future update to iOS.
-Dave
- michaelyorkFrequent Contributor
Can also confirm that even today's updated (public release) build of iOS 17.1 did not include the fix from earlier betas.