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
I'm using the legacy Bitwarden app pubicly available in App Store / Play Store and I'm aware that Bitwarden Beta bugs should be reported in bitwarden/android or bitwarden/ios
Steps To Reproduce
Create key in browser and then use in mobile app use case:
Set up PayPal passkey on bitwarden through Chrome Android (web site)
Try logging into the PayPal web site using the passkey - confirm that it works
Try logging into PayPal Android app - verify that it fails with the "asset link" error
Create key in mobile app use case:
Login to Bitwarden (from Play Store, not beta), enable Bitwarden as Passkey provider in the system
Login to PayPal app (from Play Store)
Go into PayPal profile settings and "Create Passkey"
Choose to create the passkey in Bitwarden
Expected Result
The passkey is created or able to be used successfully
Actual Result
"asset link" error
Screenshots or Videos
No response
Additional Context
In the use case where we create key in browser in bitwarden that same key created on an Android phone is able to be used to sign into the iOS version of PayPal app
Operating System
Android
Operating System Version
14
Device
Galaxy S24 Ultra
Build Version
2024.7.1
The text was updated successfully, but these errors were encountered:
Production Build
Steps To Reproduce
Create key in browser and then use in mobile app use case:
Create key in mobile app use case:
Expected Result
The passkey is created or able to be used successfully
Actual Result
"asset link" error
Screenshots or Videos
No response
Additional Context
In the use case where we create key in browser in bitwarden that same key created on an Android phone is able to be used to sign into the iOS version of PayPal app
Operating System
Android
Operating System Version
14
Device
Galaxy S24 Ultra
Build Version
2024.7.1
The text was updated successfully, but these errors were encountered: