"Unable to create passkey" on PayPal
There were some updates to the PayPal app recently (8.54.2) and I noticed that it now tries to use third-party passkey managers (1PW). Unfortunately, trying to have it create a passkey in 1PW causes it to fail:
1Password Version: 8.10.24-30.BETA
Extension Version: Not Provided
OS Version: Android 14 (Jan 5 2024)
Browser: Not Provided
Comments
-
Hi @tvandinter,
This is an issue we have been able to reproduce on our end. We have an issue logged for this with our development team who are investigating the issue.
I hope this helps.
-- Brendan
ref: dev/core/core#26762
1 -
0
-
Hi @nicos18,
From checking on our end I can see this issue is still being investigated.
With that said, while it may not be ideal, I was able to create a passkey for Paypal on my own device via the Paypal website in my Chrome browser. Once the passkey was created via the Chrome browser, I was then able to sign in to the Paypal app using this passkey.
If you create the passkey via your web browser on the Paypal website, would you then be able to use this passkey to sign into the Paypal app on your device?
-- Brendan
0 -
Hi @BrendanR1P,
I tried to create a passkey via Chrome browser, but I wasn't able to select 1Password because I was prompted to save the passkey in my Google account.
I have an S23 with Android 14.
1 -
Hi @nicos18,
Currently by default Chrome and other Chromium based browsers doesn't appear to have Credential Management enabled by default. This would be required for third party password managers such as 1Password to allow you to sign in to websites using passkeys. This would likely be why you are being prompted to save the passkey to your Google account rather than 1Password.
While we would be unable to provide a timeframe for when Google will have this enabled by default, it's possible to enable Credential Management within the Flags feature of Chrome which should allow you to use 1Password to sign into websites with passkeys. Please note, enabling and disabling particular flags can potentially lead to instability within your web browser, please ensure only the changes mentioned below are made and if you encounter any stability issues after setting these flags, please set them back to default.
Enabling Credential Management flag in Chrome
- Open Chrome, then type in chrome://flags into the address bar
- In the flags page which opens, tap the search box, then search for passkeys
- Tap Default under the Android Credential Management for passkeys flag, then tap Enable for Google Password Manager and 3rd party passkeys
- Click the Relaunch button that appears at the bottom of your browser
I hope this helps.
-- Brendan
2 -
Hi @BrendanR1P,
I was able to create a passkey for PayPal in Chrome browser by selecting the option "Enable for Google Password Manager and 3rd party passkeys".
Thanks.
2 -
Hi @nicos18,
You're very welcome. Thanks for sharing this update. I'm glad to hear you were able to create a passkey for Paypal in Chrome.
-- Brendan
1 -
I was able to reproduce the bug and the workaround. I also had to select "Enable for Google Password Manager and 3rd party passkeys".
0 -
Hi @IanPaulF,
Thanks for sharing that you also had to select "Enable for Google Password Manager and 3rd party passkeys" for this to work correctly.
I've updated the steps in my reply above to reflect this.
Thanks,
-- Brendan
0 -
I'm having the same issue where I cannot create a passkey with 1Password with the PayPal app, on a Samsung Galaxy S21. I am able to select 1Password to save the passkey, but then 1Password gives the error "Unable to create passkey. The website or service failed to send required details to 1Password."
For now it's not worth the effort to figure out that Chrome workaround, I'd rather wait for the defaults to "just work".
0 -
Hi @nukmicah,
From checking on our end I can see this issue is still being investigated.
When a fix for the issue has been released in an update to the 1Password for Android app, it will be mentioned in our release notes on the following link - 1Password for Android Releases
I apologise for any inconvenience this issue has caused
-- Brendan
0