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
Invoke a FIDO:/ schema-prefixed URI (like FIDO:/13086400838107303667332719012595115747821895775708323189557153075146383351399743589971313508078026948312026786722471666005727649643501784024544726574771401798171307406596245). 1
I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
Steps To Reproduce
com.google.android.gms
.v2024.11.7/com.x8bit.bitwarden-standard-beta.aab
FIDO:/
schema-prefixed URI (likeFIDO:/13086400838107303667332719012595115747821895775708323189557153075146383351399743589971313508078026948312026786722471666005727649643501784024544726574771401798171307406596245
). 1Expected Result
com.x8bit.bitwarden
should have intercepted the activity, because it does when usingaddons.mozilla.org/firefox/downloads/file/4392295/bitwarden_password_manager-2024.11.2.xpi
on:firefox-nightly-for-developers-135-0a1-5-android-apk
41/fedora-updates-x86_64/firefox-133.0-2.fc41.x86_64.rpm
Actual Result
The default handler appears to be
com.google.android.gms/.fido.fido2.ui.hybrid.HybridAuthenticateActivity
. 2Screenshots or Videos
I possess them, but don't want to upload them yet because I don't know whether displaying a real FIDO URI is insecure.
Additional Context
How can I open my app from a URI scheme (deep link) airsdk/Adobe-Runtime-Support#2451 (comment) appears to explain somewhat how to implement the association.
stackoverflow.com/revisions/75651445/6
explains how to decode such a URI.Build Version
v2024.11.7/com.x8bit.bitwarden-standard-beta.aab
What server are you connecting to?
US
Environment Details
#!/usr/bin/env -S bash adb shell getprop
Issue Tracking Info
Footnotes
stackoverflow.com/revisions/75651445/6
↩android.stackexchange.com/revisions/258784/3
↩The text was updated successfully, but these errors were encountered: