You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There seems to be a bug related to hand-off of Passkeys, either in Dashlane or iOS itself.
Today I was attempting to complete a payment transaction using PayPal. Normally I provide my PayPal credentials via Dashlane. This time, I got a dialog at the bottom on the screen that reads Sign in to paypal.com using a passkey from Dashlane? The blue button says Use "[my email address]", but tapping on this button does nothing and the dialog stays visible even after repeated taps. Below the button, icons for keyboard entry or the password manager are also visible.
I was eventually able to work around this by backing out and entering my PayPal information manually. Before doing so I tried to use a Passkey again but was unsuccessful for the reason outlined above.
I have a screen capture of the problematic dialog in case it is of any use, but would prefer not to post it here.
The text was updated successfully, but these errors were encountered:
There seems to be a bug related to hand-off of Passkeys, either in Dashlane or iOS itself.
Today I was attempting to complete a payment transaction using PayPal. Normally I provide my PayPal credentials via Dashlane. This time, I got a dialog at the bottom on the screen that reads
Sign in to paypal.com using a passkey from Dashlane?
The blue button saysUse "[my email address]"
, but tapping on this button does nothing and the dialog stays visible even after repeated taps. Below the button, icons for keyboard entry or the password manager are also visible.I was eventually able to work around this by backing out and entering my PayPal information manually. Before doing so I tried to use a Passkey again but was unsuccessful for the reason outlined above.
I have a screen capture of the problematic dialog in case it is of any use, but would prefer not to post it here.
The text was updated successfully, but these errors were encountered: