github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-05-06 07:48:22 -05:00
Code Issues 1.1k Packages Projects Releases 122 Wiki Activity

[GH-ISSUE #5329] Unable to create passkey for WhatsApp #50334

New Issue
Closed
opened 2026-05-01 12:33:13 -05:00 by GiteaMirror · 63 comments
GiteaMirror commented 2026-05-01 12:33:13 -05:00
Owner
Copy Link

Originally created by @oleglucic on GitHub (Jun 8, 2025).
Original GitHub issue: https://github.com/bitwarden/android/issues/5329

Steps To Reproduce

  1. Go to 'WhatsApp, open settings and attempt to create a passkey'
  2. You will be prompted to save it to Bitwarden, do that
  3. You will get an error from bitwarden (This app doesn't support passkey)

Expected Result

It should create passkey for whatsapp as usual

Actual Result

it returns error that the app doesn't support passkey

Screenshots or Videos

No response

Additional Context

No response

Build Version

2025.5.0 (20269)

What server are you connecting to?

US

Self-host Server Version

No response

Environment Details

© Bitwarden Inc. 2015-2025

Version: 2025.5.0 (20269)
📱 samsung SM-A145R 🤖 14@34 📦 prod
🧱 commit: 1e665db8ae
💻 build source: bitwarden/android/actions/runs/15300207138/attempts/1

Issue Tracking Info

  • 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.
Originally created by @oleglucic on GitHub (Jun 8, 2025). Original GitHub issue: https://github.com/bitwarden/android/issues/5329 ### Steps To Reproduce 1. Go to 'WhatsApp, open settings and attempt to create a passkey' 2. You will be prompted to save it to Bitwarden, do that 3. You will get an error from bitwarden (This app doesn't support passkey) ### Expected Result It should create passkey for whatsapp as usual ### Actual Result it returns error that the app doesn't support passkey ### Screenshots or Videos _No response_ ### Additional Context _No response_ ### Build Version 2025.5.0 (20269) ### What server are you connecting to? US ### Self-host Server Version _No response_ ### Environment Details © Bitwarden Inc. 2015-2025 Version: 2025.5.0 (20269) 📱 samsung SM-A145R 🤖 14@34 📦 prod 🧱 commit: https://github.com/bitwarden/android/commit/1e665db8aeb92989bdc7e312506cddd4887cde8e 💻 build source: bitwarden/android/actions/runs/15300207138/attempts/1 ### Issue Tracking Info - [x] 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.
GiteaMirror added the bugbug-passkeyapp:password-manager labels 2026-05-01 12:33:13 -05:00
GiteaMirror commented 2026-05-01 12:33:19 -05:00
Author
Owner
Copy Link

@bitwarden-bot commented on GitHub (Jun 8, 2025):

Thank you for your report! We've added this to our internal board for review.
ID: PM-22479

<!-- gh-comment-id:2954097103 --> @bitwarden-bot commented on GitHub (Jun 8, 2025): Thank you for your report! We've added this to our internal board for review. ID: PM-22479
GiteaMirror commented 2026-05-01 12:33:20 -05:00
Author
Owner
Copy Link

@abergs commented on GitHub (Jun 8, 2025):

Hey @oleglucic! Thanks for submitting this. We are aware of this bug and we're working with the WhatsApp team to adress it.

<!-- gh-comment-id:2954140330 --> @abergs commented on GitHub (Jun 8, 2025): Hey @oleglucic! Thanks for submitting this. We are aware of this bug and we're working with the WhatsApp team to adress it.
GiteaMirror commented 2026-05-01 12:33:21 -05:00
Author
Owner
Copy Link

@oleglucic commented on GitHub (Jun 8, 2025):

Glad to hear that! Looking forward to the fix : )

<!-- gh-comment-id:2954143789 --> @oleglucic commented on GitHub (Jun 8, 2025): Glad to hear that! Looking forward to the fix : )
GiteaMirror commented 2026-05-01 12:33:22 -05:00
Author
Owner
Copy Link

@Clonkex commented on GitHub (Jun 16, 2025):

I'm getting the same issue with the ubank app (yes, the same ubank app with which passkeys were broken a few months ago, sigh). Are they related or should I open a new issue?

And yes I am frustrated and concerned that such critical infrastructure is so unreliable. I love the concept of passkeys, but not being able to access my bank account is a serious issue. At least with passwords if the autofill fails you can still manually copy-paste or type, but passkeys are a black box with no manual backup.

<!-- gh-comment-id:2975157588 --> @Clonkex commented on GitHub (Jun 16, 2025): I'm getting the same issue with the ubank app (yes, the same ubank app with which passkeys were broken a few months ago, sigh). Are they related or should I open a new issue? And yes I am frustrated and concerned that such critical infrastructure is so unreliable. I love the concept of passkeys, but not being able to access my bank account is a serious issue. At least with passwords if the autofill fails you can still manually copy-paste or type, but passkeys are a black box with no manual backup.
GiteaMirror commented 2026-05-01 12:33:23 -05:00
Author
Owner
Copy Link

@abergs commented on GitHub (Jun 16, 2025):

@Clonkex I understand your concern. We've found the ubank issue and there is a fix on the way.

Do you also have a problem with WhatsApp?

<!-- gh-comment-id:2975319116 --> @abergs commented on GitHub (Jun 16, 2025): @Clonkex I understand your concern. We've found the ubank issue and there is a fix on the way. Do you also have a problem with WhatsApp?
GiteaMirror commented 2026-05-01 12:33:24 -05:00
Author
Owner
Copy Link

@Clonkex commented on GitHub (Jun 16, 2025):

@abergs I don't use WhatsApp so I can't test, sorry.

<!-- gh-comment-id:2975733844 --> @Clonkex commented on GitHub (Jun 16, 2025): @abergs I don't use WhatsApp so I can't test, sorry.
GiteaMirror commented 2026-05-01 12:33:26 -05:00
Author
Owner
Copy Link

@oleglucic commented on GitHub (Jun 28, 2025):

Is it just me or passkeys don't work for any app, just websites?

<!-- gh-comment-id:3015227655 --> @oleglucic commented on GitHub (Jun 28, 2025): Is it just me or passkeys don't work for any app, just websites?
GiteaMirror commented 2026-05-01 12:33:27 -05:00
Author
Owner
Copy Link

@mostafaqanbaryan commented on GitHub (Jun 30, 2025):

Is it just me or passkeys don't work for any app, just websites?

I've just tested Whatsapp, and works fine.
Android 15, latest bitwarden client.

<!-- gh-comment-id:3017817765 --> @mostafaqanbaryan commented on GitHub (Jun 30, 2025): > Is it just me or passkeys don't work for any app, just websites? I've just tested Whatsapp, and works fine. Android 15, latest bitwarden client.
GiteaMirror commented 2026-05-01 12:33:29 -05:00
Author
Owner
Copy Link

@oleglucic commented on GitHub (Jun 30, 2025):

Doesn't work for me. No app passkey works for me.

<!-- gh-comment-id:3019757494 --> @oleglucic commented on GitHub (Jun 30, 2025): Doesn't work for me. No app passkey works for me.
GiteaMirror commented 2026-05-01 12:33:30 -05:00
Author
Owner
Copy Link

@abergs commented on GitHub (Jul 16, 2025):

@oleglucic The fact that no app passkeys work for you seems to indicate that this is a problem related to your system version, and/or settings.

Make sure you're running the latest version @oleglucic

<!-- gh-comment-id:3077550706 --> @abergs commented on GitHub (Jul 16, 2025): @oleglucic The fact that no app passkeys work for you seems to indicate that this is a problem related to your system version, and/or settings. Make sure you're running the latest version @oleglucic
GiteaMirror commented 2026-05-01 12:33:31 -05:00
Author
Owner
Copy Link

@oleglucic commented on GitHub (Jul 16, 2025):

Running the latest on One UI 7 : )

<!-- gh-comment-id:3077553859 --> @oleglucic commented on GitHub (Jul 16, 2025): Running the latest on One UI 7 : )
GiteaMirror commented 2026-05-01 12:33:32 -05:00
Author
Owner
Copy Link

@abergs commented on GitHub (Jul 16, 2025):

@oleglucic Thanks for the speedy reply. What BW version are you running?

And have you enabled BW as the system passkey provider? Do passkeys work on websites?

<!-- gh-comment-id:3077565603 --> @abergs commented on GitHub (Jul 16, 2025): @oleglucic Thanks for the speedy reply. What BW version are you running? And have you enabled BW as the system passkey provider? Do passkeys work on websites?
GiteaMirror commented 2026-05-01 12:33:35 -05:00
Author
Owner
Copy Link

@oleglucic commented on GitHub (Jul 16, 2025):

I have and they work on websites

Here are the specs:
© Bitwarden Inc. 2015-2025

Version: 2025.6.1 (20398)
📱 samsung SM-G996B 🤖 15@35 📦 prod
🧱 commit: bitwarden/android/release/hotfix-v2025.6.0-bwpm@e8878d321546a846909c70c00cdf8d7071f0ecf0
💻 build source: bitwarden/android/actions/runs/15984517798/attempts/1

<!-- gh-comment-id:3077571279 --> @oleglucic commented on GitHub (Jul 16, 2025): I have and they work on websites Here are the specs: © Bitwarden Inc. 2015-2025 Version: 2025.6.1 (20398) 📱 samsung SM-G996B 🤖 15@35 📦 prod 🧱 commit: bitwarden/android/release/hotfix-v2025.6.0-bwpm@e8878d321546a846909c70c00cdf8d7071f0ecf0 💻 build source: bitwarden/android/actions/runs/15984517798/attempts/1
GiteaMirror commented 2026-05-01 12:33:37 -05:00
Author
Owner
Copy Link

@abergs commented on GitHub (Jul 16, 2025):

In you original post you shared: "You will get an error from bitwarden (This app doesn't support passkey)".

Is this what's happening on all apps?

<!-- gh-comment-id:3077608974 --> @abergs commented on GitHub (Jul 16, 2025): In you original post you shared: "You will get an error from bitwarden (This app doesn't support passkey)". Is this what's happening on all apps?
GiteaMirror commented 2026-05-01 12:33:40 -05:00
Author
Owner
Copy Link

@oleglucic commented on GitHub (Jul 26, 2025):

Yes. Sorry for the late response : )

<!-- gh-comment-id:3123481681 --> @oleglucic commented on GitHub (Jul 26, 2025): Yes. Sorry for the late response : )
GiteaMirror commented 2026-05-01 12:33:41 -05:00
Author
Owner
Copy Link

@Joolee commented on GitHub (Oct 29, 2025):

I can confirm this issue with WhatsApp and other apps. Getting the same error "Passkeys not supported for this app"
© Bitwarden Inc. 2015-2025

Version: 2025.10.0 (20794)
📱 motorola motorola razr 50 ultra 🤖 15@35 📦 prod
🧱 commit: bitwarden/android/release/2025.10-rc36@acc9113f9ad9b285e176375b6dc1db4249c3ae61
💻 build source: bitwarden/android/actions/runs/18227627683/attempts/1
🦀 SDK: 1.0.0-3194-9947387b
🌩 Server: 2025.10.1 @ US

<!-- gh-comment-id:3463231519 --> @Joolee commented on GitHub (Oct 29, 2025): I can confirm this issue with WhatsApp and other apps. Getting the same error "Passkeys not supported for this app" © Bitwarden Inc. 2015-2025 Version: 2025.10.0 (20794) 📱 motorola motorola razr 50 ultra 🤖 15@35 📦 prod 🧱 commit: bitwarden/android/release/2025.10-rc36@acc9113f9ad9b285e176375b6dc1db4249c3ae61 💻 build source: bitwarden/android/actions/runs/18227627683/attempts/1 🦀 SDK: 1.0.0-3194-9947387b 🌩 Server: 2025.10.1 @ US
GiteaMirror commented 2026-05-01 12:33:42 -05:00
Author
Owner
Copy Link

@Zeusina commented on GitHub (Nov 3, 2025):

Same issue with message: Failed to create access key. To resolve this issue, please check the access key requirements in the Help Center.

© Bitwarden Inc. 2015-2025

Version: 2025.10.1 (20867)
📱 samsung SM-S936B 🤖 16@36 📦 prod
🧱 commit: bitwarden/android/release/2025.10-rc37@74b9a12e19e07b60271a1141d3a95f7919811ea4
💻 build source: bitwarden/android/actions/runs/18598736732/attempts/1
🦀 SDK: 1.0.0-3430-fc75b903
🌩 Server: Vaultwarden 2025.6.0

<!-- gh-comment-id:3479314487 --> @Zeusina commented on GitHub (Nov 3, 2025): Same issue with message: Failed to create access key. To resolve this issue, please check the access key requirements in the Help Center. © Bitwarden Inc. 2015-2025 Version: 2025.10.1 (20867) 📱 samsung SM-S936B 🤖 16@36 📦 prod 🧱 commit: bitwarden/android/release/2025.10-rc37@74b9a12e19e07b60271a1141d3a95f7919811ea4 💻 build source: bitwarden/android/actions/runs/18598736732/attempts/1 🦀 SDK: 1.0.0-3430-fc75b903 🌩 Server: Vaultwarden 2025.6.0
GiteaMirror commented 2026-05-01 12:33:45 -05:00
Author
Owner
Copy Link

@Yolakalemowa commented on GitHub (Nov 6, 2025):

Hi, I found this issue trying to solve my problem.
My phone is Tecno Spark. I'm trying to setup passkeys for whatsapp. But by default, after clicking "create" it shows me the google password manager popup and no option to choose bitwarden.

Furthermore, I was checking the BW documentations and found this:

Image

but I couldn't find the "passkey management" option mentioned.

Could you advise? thank you so much

<!-- gh-comment-id:3496117373 --> @Yolakalemowa commented on GitHub (Nov 6, 2025): Hi, I found this issue trying to solve my problem. My phone is Tecno Spark. I'm trying to setup passkeys for whatsapp. But by default, after clicking "create" it shows me the google password manager popup and no option to choose bitwarden. Furthermore, I was checking the BW [documentations ](https://bitwarden.com/help/storing-passkeys/#tab-android-3XutklkReT3Gw0l1qHhBem) and found this: <img width="611" height="339" alt="Image" src="https://github.com/user-attachments/assets/7c15770f-23e4-4c91-ab17-7f90b39348fd" /> but I couldn't find the "passkey management" option mentioned. Could you advise? thank you so much
GiteaMirror commented 2026-05-01 12:33:47 -05:00
Author
Owner
Copy Link

@pamperer562580892423 commented on GitHub (Nov 6, 2025):

@Yolakalemowa What is your Android version? -- You need at least Android 14 for "third-party passkey management".

<!-- gh-comment-id:3497435992 --> @pamperer562580892423 commented on GitHub (Nov 6, 2025): @Yolakalemowa What is your Android version? -- You need at least Android 14 for "third-party passkey management".
GiteaMirror commented 2026-05-01 12:33:49 -05:00
Author
Owner
Copy Link

@xhemp commented on GitHub (Nov 6, 2025):

I'm on Android 16 and use it on websites and some other apps but for WhatsApp, it doesn't work.

<!-- gh-comment-id:3497480489 --> @xhemp commented on GitHub (Nov 6, 2025): I'm on Android 16 and use it on websites and some other apps but for WhatsApp, it doesn't work.
GiteaMirror commented 2026-05-01 12:33:52 -05:00
Author
Owner
Copy Link

@yodasad commented on GitHub (Nov 12, 2025):

Android 15, the same issue

<!-- gh-comment-id:3520001529 --> @yodasad commented on GitHub (Nov 12, 2025): Android 15, the same issue
GiteaMirror commented 2026-05-01 12:33:55 -05:00
Author
Owner
Copy Link

@Belsedar commented on GitHub (Nov 12, 2025):

Android 16 same issue (bitwarden is selected as the "Passwords, passkeys and accounts" service)

<!-- gh-comment-id:3521113077 --> @Belsedar commented on GitHub (Nov 12, 2025): Android 16 same issue (bitwarden is selected as the "Passwords, passkeys and accounts" service)
GiteaMirror commented 2026-05-01 12:33:59 -05:00
Author
Owner
Copy Link

@4erdenko commented on GitHub (Nov 13, 2025):

Same problem, Android 16 latest build of Bitwarden. Any news?

<!-- gh-comment-id:3527116201 --> @4erdenko commented on GitHub (Nov 13, 2025): Same problem, Android 16 latest build of Bitwarden. Any news?
GiteaMirror commented 2026-05-01 12:34:05 -05:00
Author
Owner
Copy Link

@ShamanLesnoy commented on GitHub (Nov 17, 2025):

Same problem, Android 16 latest build of Bitwarden. Any news?

Nothing:( Same problem. I wrote to support by email, but they gave me link for this issue

<!-- gh-comment-id:3539520014 --> @ShamanLesnoy commented on GitHub (Nov 17, 2025): > Same problem, Android 16 latest build of Bitwarden. Any news? Nothing:( Same problem. I wrote to support by email, but they gave me link for this issue
GiteaMirror commented 2026-05-01 12:34:07 -05:00
Author
Owner
Copy Link

@abergs commented on GitHub (Nov 17, 2025):

Thanks all for making us aware of this and providing your OS versions. We're still trying to identify why WhatsApp is not working and getting ahold of their team to see where the misalignment is happening.

<!-- gh-comment-id:3540613458 --> @abergs commented on GitHub (Nov 17, 2025): Thanks all for making us aware of this and providing your OS versions. We're still trying to identify why WhatsApp is not working and getting ahold of their team to see where the misalignment is happening.
GiteaMirror commented 2026-05-01 12:34:09 -05:00
Author
Owner
Copy Link

@Joolee commented on GitHub (Nov 17, 2025):

The problem is not confined to just WhatsApp. Trying to create Passkeys for other apps fails too. I have just now logged in to GitHub using a Bitwarden passkey using Firefox so it seems to be confined to apps other than webbrowsers.

<!-- gh-comment-id:3540667223 --> @Joolee commented on GitHub (Nov 17, 2025): The problem is not confined to just WhatsApp. Trying to create Passkeys for other apps fails too. I have just now logged in to GitHub using a Bitwarden passkey using Firefox so it seems to be confined to apps other than webbrowsers.
GiteaMirror commented 2026-05-01 12:34:11 -05:00
Author
Owner
Copy Link

@abergs commented on GitHub (Nov 17, 2025):

@Joolee What apps? Having as much details as possible, like OS versions and apps versions is useful, since we're seeing passkeys work on almost all apps on android in our own testing.

<!-- gh-comment-id:3540682787 --> @abergs commented on GitHub (Nov 17, 2025): @Joolee What apps? Having as much details as possible, like OS versions and apps versions is useful, since we're seeing passkeys work on almost all apps on android in our own testing.
GiteaMirror commented 2026-05-01 12:34:19 -05:00
Author
Owner
Copy Link

@drizzt09 commented on GitHub (Nov 18, 2025):

Same for Facebook app on android

<!-- gh-comment-id:3549492874 --> @drizzt09 commented on GitHub (Nov 18, 2025): Same for Facebook app on android
GiteaMirror commented 2026-05-01 12:34:27 -05:00
Author
Owner
Copy Link

@gvlf commented on GitHub (Nov 19, 2025):

I have just tried to add a passkey from Notion and Whatsapp and the same happens on both of them, but Facebook works normally. Here are the logs of that through flight recorder, when I tried to add the passkeys starting with WhatsApp, then Notion and finally Facebook. My phone is Xiaomi 15T Pro on Android 16 with HyperOS 3.0.5.0WOSEUXM.
I did the test on version 20867, but after updating to 20967 nothing changed.
bitwarden_flight_recorder8030926306049758610.zip

<!-- gh-comment-id:3555038230 --> @gvlf commented on GitHub (Nov 19, 2025): I have just tried to add a passkey from Notion and Whatsapp and the same happens on both of them, but Facebook works normally. Here are the logs of that through flight recorder, when I tried to add the passkeys starting with WhatsApp, then Notion and finally Facebook. My phone is Xiaomi 15T Pro on Android 16 with HyperOS 3.0.5.0WOSEUXM. I did the test on version 20867, but after updating to 20967 nothing changed. [bitwarden_flight_recorder8030926306049758610.zip](https://github.com/user-attachments/files/23638876/bitwarden_flight_recorder8030926306049758610.zip)
GiteaMirror commented 2026-05-01 12:34:28 -05:00
Author
Owner
Copy Link

@SaintPatrck commented on GitHub (Nov 20, 2025):

@gvlf Notion is failing due to a redirect encountered when attempting to verify the app's authenticity via their assetlinks.json. More details on that can be found in issue #6164.

We've identified the root cause of WhatsApp failures. It is also related to verifying the authenticity of the application. It appears that WhatsApp has recently rotated to a new APK signing key1 for their application but have not updated their assetlinks.json file to include the new key signature. It is currently unclear why the keys were rotated. We are actively investigating solutions that do not compromise security.

  1. FB:92:0D:38:1B:EE:1B:20:93:F2:7D:C8:F1:3D:99:4D:A6:29:DC:91:88:7D:05:29:B3:5C:9A:2D:C4:F4:A6:C2 ↩︎

<!-- gh-comment-id:3557970040 --> @SaintPatrck commented on GitHub (Nov 20, 2025): @gvlf Notion is failing due to a redirect encountered when attempting to verify the app's authenticity via their `assetlinks.json`. More details on that can be found in issue #6164. We've identified the root cause of WhatsApp failures. It is also related to verifying the authenticity of the application. It appears that WhatsApp has recently rotated to a new APK signing key[^1] for their application but have not updated their [assetlinks.json](https://whatsapp.com/.well-known/assetlinks.json) file to include the new key signature. It is currently unclear why the keys were rotated. We are actively investigating solutions that do not compromise security. [^1]: `FB:92:0D:38:1B:EE:1B:20:93:F2:7D:C8:F1:3D:99:4D:A6:29:DC:91:88:7D:05:29:B3:5C:9A:2D:C4:F4:A6:C2`
GiteaMirror commented 2026-05-01 12:34:29 -05:00
Author
Owner
Copy Link

@ShamanLesnoy commented on GitHub (Nov 21, 2025):

WhatsApp - a bunch of clowns and idiots

<!-- gh-comment-id:3562220183 --> @ShamanLesnoy commented on GitHub (Nov 21, 2025): WhatsApp - a bunch of clowns and idiots
GiteaMirror commented 2026-05-01 12:34:31 -05:00
Author
Owner
Copy Link

@RokeJulianLockhart commented on GitHub (Nov 30, 2025):

This appears to relate to bitwarden/mobile/issues/3226.

<!-- gh-comment-id:3592544309 --> @RokeJulianLockhart commented on GitHub (Nov 30, 2025): This appears to relate to [`bitwarden/mobile/issues/3226`](https://github.com/bitwarden/mobile/issues/3226#issue-2363251444).
GiteaMirror commented 2026-05-01 12:34:36 -05:00
Author
Owner
Copy Link

@yodasad commented on GitHub (Dec 8, 2025):

Passkey works in Telegram for Android

<!-- gh-comment-id:3624606237 --> @yodasad commented on GitHub (Dec 8, 2025): Passkey works in Telegram for Android
GiteaMirror commented 2026-05-01 12:34:41 -05:00
Author
Owner
Copy Link

@yeezylife commented on GitHub (Dec 10, 2025):

Passkey works in Telegram for Android

not for me (android 15) it shows no dependency found blah blah blah

<!-- gh-comment-id:3635032925 --> @yeezylife commented on GitHub (Dec 10, 2025): > Passkey works in Telegram for Android not for me (android 15) it shows no dependency found blah blah blah
GiteaMirror commented 2026-05-01 12:34:42 -05:00
Author
Owner
Copy Link

@pamperer562580892423 commented on GitHub (Dec 10, 2025):

Passkey works in Telegram for Android

not for me (android 15) it shows no dependency found blah blah blah

Probably off-topic for this WhatsApp-issue, but I could successfully store a Telegram passkey in BW (Android 15).

<!-- gh-comment-id:3635084016 --> @pamperer562580892423 commented on GitHub (Dec 10, 2025): > > Passkey works in Telegram for Android > > not for me (android 15) it shows no dependency found blah blah blah Probably off-topic for this WhatsApp-issue, but I could successfully store a Telegram passkey in BW (Android 15).
GiteaMirror commented 2026-05-01 12:34:43 -05:00
Author
Owner
Copy Link

@radupotop commented on GitHub (Dec 10, 2025):

Having this issue with WhatsApp and Revolut apps on Android.

Samsung S23, Android 16.

<!-- gh-comment-id:3635093178 --> @radupotop commented on GitHub (Dec 10, 2025): Having this issue with WhatsApp and Revolut apps on Android. Samsung S23, Android 16.
GiteaMirror commented 2026-05-01 12:34:45 -05:00
Author
Owner
Copy Link

@pamperer562580892423 commented on GitHub (Dec 10, 2025):

@radupotop

and Revolut apps on Android.

Samsung S23, Android 16.

There is a separate issue regarding the Revolut app: https://github.com/bitwarden/android/issues/6164

<!-- gh-comment-id:3635123567 --> @pamperer562580892423 commented on GitHub (Dec 10, 2025): @radupotop > and Revolut apps on Android. > > Samsung S23, Android 16. There is a separate issue regarding the Revolut app: https://github.com/bitwarden/android/issues/6164
GiteaMirror commented 2026-05-01 12:34:48 -05:00
Author
Owner
Copy Link

@EithonX commented on GitHub (Dec 23, 2025):

Whatsapp, Facebook passkey creation doesn't work. I wonder when are we gonna get a fix for this.

<!-- gh-comment-id:3686921810 --> @EithonX commented on GitHub (Dec 23, 2025): Whatsapp, Facebook passkey creation doesn't work. I wonder when are we gonna get a fix for this.
GiteaMirror commented 2026-05-01 12:34:50 -05:00
Author
Owner
Copy Link

@ashdkv commented on GitHub (Dec 24, 2025):

NP2, A16, dont work also. Please fix it.

<!-- gh-comment-id:3690473826 --> @ashdkv commented on GitHub (Dec 24, 2025): NP2, A16, dont work also. Please fix it.
GiteaMirror commented 2026-05-01 12:34:55 -05:00
Author
Owner
Copy Link

@pamperer562580892423 commented on GitHub (Dec 27, 2025):

@EithonX @ashdkv See the latest update by a BW developer: https://github.com/bitwarden/android/issues/5329#issuecomment-3557970040

<!-- gh-comment-id:3694131731 --> @pamperer562580892423 commented on GitHub (Dec 27, 2025): @EithonX @ashdkv See the latest update by a BW developer: https://github.com/bitwarden/android/issues/5329#issuecomment-3557970040
GiteaMirror commented 2026-05-01 12:35:01 -05:00
Author
Owner
Copy Link

@Lord-Of-Mysteries404 commented on GitHub (Jan 3, 2026):

Doesn't work for me either

<!-- gh-comment-id:3707288674 --> @Lord-Of-Mysteries404 commented on GitHub (Jan 3, 2026): Doesn't work for me either
GiteaMirror commented 2026-05-01 12:35:08 -05:00
Author
Owner
Copy Link

@neosis91 commented on GitHub (Jan 12, 2026):

Creation of passkey with whatsapp doesn't work

<!-- gh-comment-id:3738242711 --> @neosis91 commented on GitHub (Jan 12, 2026): Creation of passkey with whatsapp doesn't work
GiteaMirror commented 2026-05-01 12:35:11 -05:00
Author
Owner
Copy Link

@brianjmurrell commented on GitHub (Jan 12, 2026):

Creation of passkey with whatsapp doesn't work

What a useful comment.

How do you think it's helpful to add a comment that simply restates the topic and very core nature of the reported issue? Moreover, have that comment be sent out to the e-mail boxes of all of the people who have subscribed to this issue, which they have done so that they get notified when something actually useful and important is added to the ticket -- like the issue has been fixed.

If you want to subscribe to this issue so that you get updates you can do that without sending out thousands of useless "me too" e-mails by adding useless comments. You can use the Subscribe button for that.

If you want to show your support for having the issue fixed you can use thumbs up emojis and such. You do not not need to pollute the e-mail boxes of thousands of users with useless "me too" comments. See the initial comment for two such emojis that you could have clicked rather than sending thousands of people a useless "me too".

And yes, I understand the irony of my comment here, but I do it hoping I can head of a few more hundred (or maybe thousand) useless "me too" comments.

<!-- gh-comment-id:3738640044 --> @brianjmurrell commented on GitHub (Jan 12, 2026): > Creation of passkey with whatsapp doesn't work What a useful comment. How do you think it's helpful to add a comment that simply restates the topic and very core nature of the reported issue? Moreover, have that comment be sent out to the e-mail boxes of all of the people who have subscribed to this issue, which they have done so that they get notified when something actually useful and **important** is added to the ticket -- like the issue has been fixed. If you want to subscribe to this issue so that you get updates you can do that without sending out thousands of useless "me too" e-mails by adding useless comments. You can use the **Subscribe** button for that. If you want to show your support for having the issue fixed you can use thumbs up emojis and such. You do not not need to pollute the e-mail boxes of thousands of users with useless "me too" comments. See the initial comment for two such emojis that you could have clicked rather than sending thousands of people a useless "me too". And yes, I understand the irony of my comment here, but I do it hoping I can head of a few more hundred (or maybe thousand) useless "me too" comments.
GiteaMirror commented 2026-05-01 12:35:13 -05:00
Author
Owner
Copy Link

@neosis91 commented on GitHub (Jan 12, 2026):

Sorry about my comment — I thought I was doing the right thing by reacting, but I understand it might have been annoying by sending unnecessary notifications.

<!-- gh-comment-id:3738686394 --> @neosis91 commented on GitHub (Jan 12, 2026): Sorry about my comment — I thought I was doing the right thing by reacting, but I understand it might have been annoying by sending unnecessary notifications.
GiteaMirror commented 2026-05-01 12:35:14 -05:00
Author
Owner
Copy Link

@EithonX commented on GitHub (Jan 12, 2026):

Creation of passkey with whatsapp doesn't work

What a useful comment.

How do you think it's helpful to add a comment that simply restates the topic and very core nature of the reported issue? Moreover, have that comment be sent out to the e-mail boxes of all of the people who have subscribed to this issue, which they have done so that they get notified when something actually useful and important is added to the ticket -- like the issue has been fixed.

If you want to subscribe to this issue so that you get updates you can do that without sending out thousands of useless "me too" e-mails by adding useless comments. You can use the Subscribe button for that.

If you want to show your support for having the issue fixed you can use thumbs up emojis and such. You do not not need to pollute the e-mail boxes of thousands of users with useless "me too" comments. See the initial comment for two such emojis that you could have clicked rather than sending thousands of people a useless "me too".

And yes, I understand the irony of my comment here, but I do it hoping I can head of a few more hundred (or maybe thousand) useless "me too" comments.

If “me too” comments are spam, this manifesto is a ddos in my inbox. It’s not that deep. People are meant to participate to let devs know how affected they are.. Just mute it if it annoys you too much.

<!-- gh-comment-id:3738753810 --> @EithonX commented on GitHub (Jan 12, 2026): > > Creation of passkey with whatsapp doesn't work > > What a useful comment. > > How do you think it's helpful to add a comment that simply restates the topic and very core nature of the reported issue? Moreover, have that comment be sent out to the e-mail boxes of all of the people who have subscribed to this issue, which they have done so that they get notified when something actually useful and **important** is added to the ticket -- like the issue has been fixed. > > If you want to subscribe to this issue so that you get updates you can do that without sending out thousands of useless "me too" e-mails by adding useless comments. You can use the **Subscribe** button for that. > > If you want to show your support for having the issue fixed you can use thumbs up emojis and such. You do not not need to pollute the e-mail boxes of thousands of users with useless "me too" comments. See the initial comment for two such emojis that you could have clicked rather than sending thousands of people a useless "me too". > > And yes, I understand the irony of my comment here, but I do it hoping I can head of a few more hundred (or maybe thousand) useless "me too" comments. If “me too” comments are spam, this manifesto is a ddos in my inbox. It’s not that deep. People are meant to participate to let devs know how affected they are.. Just mute it if it annoys you too much.
GiteaMirror commented 2026-05-01 12:35:15 -05:00
Author
Owner
Copy Link

@pamperer562580892423 commented on GitHub (Jan 12, 2026):

I must say, I can understand both sides here.

  1. As this issue is a bug where it's expected that probably everyone is affected, just "me too" comments indeed provide no relevant new information.

  2. On the other hand, I wouldn't be too harsh about that, as even those comments show BW, that the issue (still) is relevant for users, so those comments might not be that "useless" after all...

  3. Furthermore, I do think, that no user should be forbidden (by other users) from reporting or participating in public issues here...

  4. At last, everyone who doesn't want to get new notifications, can indeed either "Unsubscribe" - or maybe even better: you can "customize" notifications and e.g. choose to only get notifications when the issue gets closed:

 

Image

 

Image
<!-- gh-comment-id:3738934859 --> @pamperer562580892423 commented on GitHub (Jan 12, 2026): I must say, I can understand both sides here. 1. As this issue is a bug where it's expected that probably everyone is affected, just "me too" comments indeed provide no relevant new information. 2. On the other hand, I wouldn't be too harsh about that, as even those comments show BW, that the issue (still) is relevant for users, so those comments might not be that "useless" after all... 3. Furthermore, I do think, that no user should be forbidden (by other users) from reporting or participating in public issues here... 4. At last, everyone who doesn't want to get new notifications, can indeed either "Unsubscribe" - or maybe even better: you can "customize" notifications and e.g. choose to only get notifications when the issue gets closed: &nbsp; <img width="695" height="475" alt="Image" src="https://github.com/user-attachments/assets/53d2bf0b-adcf-4de5-aa14-e51cb6f53d08" /> &nbsp; <img width="732" height="676" alt="Image" src="https://github.com/user-attachments/assets/4a3a2fb0-a27a-4169-a7cd-76bad54e13f0" />
GiteaMirror commented 2026-05-01 12:35:15 -05:00
Author
Owner
Copy Link

@brianjmurrell commented on GitHub (Jan 12, 2026):

  1. On the other hand, I wouldn't be too harsh about that, as even those comments show BW, that the issue (still) is relevant for users, so those comments might not be that "useless" after all...

I doubt the developers need to be continually reminded about open issues. If they feel like it might have been fixed by some recent update, they can come here and ask if anyone is still experiencing it.

  1. Furthermore, I do think, that no user should be forbidden (by other users) from reporting or participating in public issues here...

No. But they can use the accepted means of adding their interest/affectedness by clicking the emojis in the original comment as 26 others have done appropriately:

Image
  1. At last, everyone who doesn't want to get new notifications,

New useful notifications are wanted. Useless, time-wasting me too notifications are not.

can indeed either "Unsubscribe"

Again, which means not getting useful notifications.

or maybe even better: you can "customize" notifications and e.g. choose to only get notifications when the issue gets closed:> >  

Again and, not see useful notifications, like devs looking for more information to solve the problem.

<!-- gh-comment-id:3739245477 --> @brianjmurrell commented on GitHub (Jan 12, 2026): > 2. On the other hand, I wouldn't be too harsh about that, as even those comments show BW, that the issue (still) is relevant for users, so those comments might not be that "useless" after all... I doubt the developers need to be continually reminded about open issues. If they feel like it might have been fixed by some recent update, they can come here and ask if anyone is still experiencing it. > 3. Furthermore, I do think, that no user should be forbidden (by other users) from reporting or participating in public issues here... No. But they can use the accepted means of adding their interest/affectedness by clicking the emojis in the original comment as 26 others have done appropriately: <img width="158" height="65" alt="Image" src="https://github.com/user-attachments/assets/450db2f2-7b80-435d-9413-4a9fe50f9a04" /> > 4. At last, everyone who doesn't want to get new notifications, New **useful** notifications are wanted. Useless, time-wasting _me too_ notifications are not. > can indeed either "Unsubscribe" Again, which means not getting useful notifications. > or maybe even better: you can "customize" notifications and e.g. choose to only get notifications when the issue gets closed:> >   Again and, not see useful notifications, like devs looking for more information to solve the problem.
GiteaMirror commented 2026-05-01 12:35:15 -05:00
Author
Owner
Copy Link

@SaintPatrck commented on GitHub (Jan 12, 2026):

Hi all

My comment has gotten buried in the chatter, unfortunately. We identified the issue with WhatsApp and are still awaiting more information about their signature discrepancies. We will update this thread when we have more information.

<!-- gh-comment-id:3740293992 --> @SaintPatrck commented on GitHub (Jan 12, 2026): Hi all [My comment](https://github.com/bitwarden/android/issues/5329#issuecomment-3557970040) has gotten buried in the chatter, unfortunately. We identified the issue with WhatsApp and are still awaiting more information about their signature discrepancies. We will update this thread when we have more information.
GiteaMirror commented 2026-05-01 12:35:15 -05:00
Author
Owner
Copy Link

@4erdenko commented on GitHub (Jan 12, 2026):

@gvlf Notion is failing due to a redirect encountered when attempting to verify the app's authenticity via their assetlinks.json. More details on that can be found in issue #6164.

We've identified the root cause of WhatsApp failures. It is also related to verifying the authenticity of the application. It appears that WhatsApp has recently rotated to a new APK signing key1 for their application but have not updated their assetlinks.json file to include the new key signature. It is currently unclear why the keys were rotated. We are actively investigating solutions that do not compromise security.

Footnotes

1. `FB:92:0D:38:1B:EE:1B:20:93:F2:7D:C8:F1:3D:99:4D:A6:29:DC:91:88:7D:05:29:B3:5C:9A:2D:C4:F4:A6:C2` [↩](#user-content-fnref-1-6466414abccbcfa54742afd6ed984007)

Hi all

My comment has gotten buried in the chatter, unfortunately. We identified the issue with WhatsApp and are still awaiting more information about their signature discrepancies. We will update this thread when we have more information.

Hi.

Tested with the current APK from the official WhatsApp download .
SHA‑256 signing fingerprint:
39:87:D0:43:D1:0A:EF:AF:5A:87:10:B3:67:14:18:FE:57:E0:E1:9B:65:3C:9D:F8:25:58:FE:B5:FF:CE:5D:44.
This fingerprint is present in https://www.whatsapp.com/.well-known/assetlinks.json, so the Digital Asset Links check
now succeeds.
Result: passkey creation/login works in Bitwarden with this APK. If anyone still sees “passkeys not supported for this
app,” please update WhatsApp from the official source and retry.

Not from Google Play.

Image
<!-- gh-comment-id:3740518932 --> @4erdenko commented on GitHub (Jan 12, 2026): > [@gvlf](https://github.com/gvlf) Notion is failing due to a redirect encountered when attempting to verify the app's authenticity via their `assetlinks.json`. More details on that can be found in issue [#6164](https://github.com/bitwarden/android/issues/6164). > > We've identified the root cause of WhatsApp failures. It is also related to verifying the authenticity of the application. It appears that WhatsApp has recently rotated to a new APK signing key[1](#user-content-fn-1-6466414abccbcfa54742afd6ed984007) for their application but have not updated their [assetlinks.json](https://whatsapp.com/.well-known/assetlinks.json) file to include the new key signature. It is currently unclear why the keys were rotated. We are actively investigating solutions that do not compromise security. > ## Footnotes > > 1. `FB:92:0D:38:1B:EE:1B:20:93:F2:7D:C8:F1:3D:99:4D:A6:29:DC:91:88:7D:05:29:B3:5C:9A:2D:C4:F4:A6:C2` [↩](#user-content-fnref-1-6466414abccbcfa54742afd6ed984007) > Hi all > > [My comment](https://github.com/bitwarden/android/issues/5329#issuecomment-3557970040) has gotten buried in the chatter, unfortunately. We identified the issue with WhatsApp and are still awaiting more information about their signature discrepancies. We will update this thread when we have more information. Hi. Tested with the current APK from the official WhatsApp [download ](https://scontent.whatsapp.net/v/t61.25591-34/10000000_2286974198483967_4025308723538414377_n.apk/WhatsApp.apk?ccb=1-7&_nc_sid=c49adc&_nc_ohc=xKzEdPyXYMIQ7kNvwGVexbp&_nc_oc=Adl3Sa_Sm138B6ODQXBZaV-PG4ukic8YD-0KQk5omoHAyX0cs1mpmKK6y0b0wjpXLIg&_nc_zt=3&_nc_ht=scontent.whatsapp.net&_nc_gid=m49XNislYOuudzJ4KaH--g&oh=01_Q5Aa3gFD0oHHxs5yPUf7l-dWW1PcJh-lt5q9UQH-PjsUuMX0fQ&oe=698CED9F). SHA‑256 signing fingerprint: 39:87:D0:43:D1:0A:EF:AF:5A:87:10:B3:67:14:18:FE:57:E0:E1:9B:65:3C:9D:F8:25:58:FE:B5:FF:CE:5D:44. This fingerprint is present in https://www.whatsapp.com/.well-known/assetlinks.json, so the Digital Asset Links check now succeeds. Result: passkey creation/login works in Bitwarden with this APK. If anyone still sees “passkeys not supported for this app,” please update WhatsApp from the [official source](https://www.whatsapp.com/android) and retry. Not from Google Play. <img width="320" height="640" alt="Image" src="https://github.com/user-attachments/assets/5e058d4e-5347-4712-9dae-bf6d9c5214f1" />
GiteaMirror commented 2026-05-01 12:35:16 -05:00
Author
Owner
Copy Link

@pamperer562580892423 commented on GitHub (Jan 13, 2026):

@4erdenko Thanks for sharing that!

Though I'm a bit confused now.

The apk version you can download at the moment is: 2.23.12.75

The version that is installed on my phone via the Google Play Store is: 2.25.37.76

So, for one thing, if I would "upgrade" now, this would be a version downgrade, as it seems. And then, I wonder if this "function" is now exclusive for APK installations, and not to be expected anytime soon for the PlayStore versions?!?

If anyone knows more on that, would be interesting to know now...

PS: Shown to me as of today on https://www.whatsapp.com/android:

Image

Or do I interpret that info wrongly?

<!-- gh-comment-id:3745513960 --> @pamperer562580892423 commented on GitHub (Jan 13, 2026): @4erdenko Thanks for sharing that! Though I'm a bit confused now. The apk version you can download at the moment is: 2.23.12.75 The version that is installed on my phone via the Google Play Store is: 2.25.37.76 So, for one thing, if I would "upgrade" now, this would be a version downgrade, as it seems. And then, I wonder if this "function" is now exclusive for APK installations, and not to be expected anytime soon for the PlayStore versions?!? If anyone knows more on that, would be interesting to know now... PS: Shown to me as of today on https://www.whatsapp.com/android: <img width="359" height="233" alt="Image" src="https://github.com/user-attachments/assets/67667330-5420-4163-809d-10cfa4137a15" /> Or do I interpret that info wrongly?
GiteaMirror commented 2026-05-01 12:35:17 -05:00
Author
Owner
Copy Link

@radupotop commented on GitHub (Jan 13, 2026):

The APK version downloaded from
https://www.whatsapp.com/android/
is 2.26.1.77 and Passkeys now work fine.

<!-- gh-comment-id:3745541859 --> @radupotop commented on GitHub (Jan 13, 2026): The APK version downloaded from https://www.whatsapp.com/android/ is 2.26.1.77 and Passkeys now work fine.
GiteaMirror commented 2026-05-01 12:35:17 -05:00
Author
Owner
Copy Link

@drizzt09 commented on GitHub (Jan 13, 2026):

What about Facebook? Same company(Meta) and same issue.

Hi all

My comment has gotten buried in the chatter, unfortunately. We identified the issue with WhatsApp and are still awaiting more information about their signature discrepancies. We will update this thread when we have more information.

<!-- gh-comment-id:3745570230 --> @drizzt09 commented on GitHub (Jan 13, 2026): What about Facebook? Same company(Meta) and same issue. > Hi all > > [My comment](https://github.com/bitwarden/android/issues/5329#issuecomment-3557970040) has gotten buried in the chatter, unfortunately. We identified the issue with WhatsApp and are still awaiting more information about their signature discrepancies. We will update this thread when we have more information.
GiteaMirror commented 2026-05-01 12:35:18 -05:00
Author
Owner
Copy Link

@drizzt09 commented on GitHub (Jan 13, 2026):

What about Facebook? Same company(Meta) and same issue.

Hi all

My comment has gotten buried in the chatter, unfortunately. We identified the issue with WhatsApp and are still awaiting more information about their signature discrepancies. We will update this thread when we have more information.

<!-- gh-comment-id:3745570239 --> @drizzt09 commented on GitHub (Jan 13, 2026): What about Facebook? Same company(Meta) and same issue. > Hi all > > [My comment](https://github.com/bitwarden/android/issues/5329#issuecomment-3557970040) has gotten buried in the chatter, unfortunately. We identified the issue with WhatsApp and are still awaiting more information about their signature discrepancies. We will update this thread when we have more information.
GiteaMirror commented 2026-05-01 12:35:18 -05:00
Author
Owner
Copy Link

@drizzt09 commented on GitHub (Jan 13, 2026):

What about Facebook? Same company(Meta) and same issue.

Hi all

My comment has gotten buried in the chatter, unfortunately. We identified the issue with WhatsApp and are still awaiting more information about their signature discrepancies. We will update this thread when we have more information.

<!-- gh-comment-id:3745570243 --> @drizzt09 commented on GitHub (Jan 13, 2026): What about Facebook? Same company(Meta) and same issue. > Hi all > > [My comment](https://github.com/bitwarden/android/issues/5329#issuecomment-3557970040) has gotten buried in the chatter, unfortunately. We identified the issue with WhatsApp and are still awaiting more information about their signature discrepancies. We will update this thread when we have more information.
GiteaMirror commented 2026-05-01 12:35:19 -05:00
Author
Owner
Copy Link

@pamperer562580892423 commented on GitHub (Jan 13, 2026):

@radupotop

The APK version downloaded from
https://www.whatsapp.com/android/
is 2.26.1.77 and Passkeys now work fine.

Ah, thanks! So there is hope it will eventually be available on Google PlayStore as well...

<!-- gh-comment-id:3745713614 --> @pamperer562580892423 commented on GitHub (Jan 13, 2026): @radupotop > The APK version downloaded from > https://www.whatsapp.com/android/ > is 2.26.1.77 and Passkeys now work fine. Ah, thanks! So there is hope it will eventually be available on Google PlayStore as well...
GiteaMirror commented 2026-05-01 12:35:19 -05:00
Author
Owner
Copy Link

@EithonX commented on GitHub (Jan 13, 2026):

@radupotop

The APK version downloaded from
https://www.whatsapp.com/android/
is 2.26.1.77 and Passkeys now work fine.

Ah, thanks! So there is hope it will eventually be available on Google PlayStore as well...

@4erdenko Thanks for sharing that!

Though I'm a bit confused now.

The apk version you can download at the moment is: 2.23.12.75

The version that is installed on my phone via the Google Play Store is: 2.25.37.76

So, for one thing, if I would "upgrade" now, this would be a version downgrade, as it seems. And then, I wonder if this "function" is now exclusive for APK installations, and not to be expected anytime soon for the PlayStore versions?!?

If anyone knows more on that, would be interesting to know now...

PS: Shown to me as of today on https://www.whatsapp.com/android:

Image Or do I interpret that info wrongly?

Can confirm, even beta versions of whatsapp from playstore doesn't have that fingerprint unfortunately.
version 2.26.2.2
com.whatsapp

<!-- gh-comment-id:3745745012 --> @EithonX commented on GitHub (Jan 13, 2026): > [@radupotop](https://github.com/radupotop) > > > The APK version downloaded from > > https://www.whatsapp.com/android/ > > is 2.26.1.77 and Passkeys now work fine. > > Ah, thanks! So there is hope it will eventually be available on Google PlayStore as well... > [@4erdenko](https://github.com/4erdenko) Thanks for sharing that! > > Though I'm a bit confused now. > > The apk version you can download at the moment is: 2.23.12.75 > > The version that is installed on my phone via the Google Play Store is: 2.25.37.76 > > So, for one thing, if I would "upgrade" now, this would be a version downgrade, as it seems. And then, I wonder if this "function" is now exclusive for APK installations, and not to be expected anytime soon for the PlayStore versions?!? > > If anyone knows more on that, would be interesting to know now... > > PS: Shown to me as of today on https://www.whatsapp.com/android: > > <img alt="Image" width="359" height="233" src="https://private-user-images.githubusercontent.com/138042245/535231163-67667330-5420-4163-809d-10cfa4137a15.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NjgzMjg0NjQsIm5iZiI6MTc2ODMyODE2NCwicGF0aCI6Ii8xMzgwNDIyNDUvNTM1MjMxMTYzLTY3NjY3MzMwLTU0MjAtNDE2My04MDlkLTEwY2ZhNDEzN2ExNS5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjYwMTEzJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI2MDExM1QxODE2MDRaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT03ZmRlMTkyZWQ5YWJmYTQyYzFmMmFkNTg0YWQwOWUxN2RlMDYwYTUwNDQyYWYyZmFmNmM3NWNiYTgxMDE5MjY2JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.SKUlHYgwvTrrvmwPRi3wwlNoiG32hcF7LVj5pUFPTII"> > Or do I interpret that info wrongly? Can confirm, even beta versions of whatsapp from playstore doesn't have that fingerprint unfortunately. version 2.26.2.2 com.whatsapp
GiteaMirror commented 2026-05-01 12:35:19 -05:00
Author
Owner
Copy Link

@abergs commented on GitHub (Jan 14, 2026):

We're still trying to get confirmation from WhatsApp.

Facebook/meta is another kind of issue called "Related Origins", but work is being done there too and it should already work on iOS.

<!-- gh-comment-id:3748488172 --> @abergs commented on GitHub (Jan 14, 2026): We're still trying to get confirmation from WhatsApp. Facebook/meta is another kind of issue called "Related Origins", but work is being done there too and it should already work on iOS.
GiteaMirror commented 2026-05-01 12:35:19 -05:00
Author
Owner
Copy Link

@servint commented on GitHub (Jan 30, 2026):

I was able to save and use passkey for WhatsApp (installed from their website) on version 2025.12.1.
But after 2026.1 update something has broken. Can't save passkey, can't read passkey.
Same thing for Telegram and one of my banks app. Edge mobile works without issues.

If logs can help I will attach the archive here.
flight_recorder_3apps.zip

P.S - rolling back to previous version helps with these issues.

<!-- gh-comment-id:3826028726 --> @servint commented on GitHub (Jan 30, 2026): I was able to save and use passkey for WhatsApp (installed from their website) on version 2025.12.1. But after 2026.1 update something has broken. Can't save passkey, can't read passkey. Same thing for Telegram and one of my banks app. Edge mobile works without issues. If logs can help I will attach the archive here. [flight_recorder_3apps.zip](https://github.com/user-attachments/files/24974940/flight_recorder_3apps.zip) P.S - rolling back to previous version helps with these issues.
GiteaMirror commented 2026-05-01 12:35:20 -05:00
Author
Owner
Copy Link

@pamperer562580892423 commented on GitHub (Feb 9, 2026):

As Android app 2026.1.1 just arrived on my phone, I just tried to create a WhatsApp passkey again - and it worked! (with the Google Play Store version of WhatsApp)

(PS: And that seems also to indicate, that version 2026.1.1 might have passkey functions for other apps again, as it seems that was "broken" with 2026.1.0)

<!-- gh-comment-id:3873271672 --> @pamperer562580892423 commented on GitHub (Feb 9, 2026): As Android app 2026.1.1 just arrived on my phone, I just tried to create a WhatsApp passkey again - and it worked! (with the Google Play Store version of WhatsApp) (PS: And that seems also to indicate, that version 2026.1.1 might have passkey functions for other apps again, as it seems that was "broken" with 2026.1.0)
GiteaMirror commented 2026-05-01 12:35:21 -05:00
Author
Owner
Copy Link

@Vinsup commented on GitHub (Feb 10, 2026):

It has worked for me as well with both latest version of apps (I have WhatsApp beta version)

<!-- gh-comment-id:3875978230 --> @Vinsup commented on GitHub (Feb 10, 2026): It has worked for me as well with both latest version of apps (I have WhatsApp beta version)
GiteaMirror commented 2026-05-01 12:35:22 -05:00
Author
Owner
Copy Link

@colemickens commented on GitHub (Feb 10, 2026):

I was too scared to overwrite the Play Store installed version, but I can confirm it works, also!

(Now, if only WhatsApp allowed signin to web.whatsapp.com with it, but I'm guess it's some E2EE/key-exchange limitation, and a good thing so oh well).

Thanks to the Bitwarden folks for their attention and work with Meta on this!

<!-- gh-comment-id:3880848064 --> @colemickens commented on GitHub (Feb 10, 2026): I was too scared to overwrite the Play Store installed version, but I can confirm it works, also! (Now, if only WhatsApp allowed signin to web.whatsapp.com with it, but I'm guess it's some E2EE/key-exchange limitation, and a good thing so oh well). Thanks to the Bitwarden folks for their attention and work with Meta on this!
GiteaMirror commented 2026-05-01 12:35:24 -05:00
Author
Owner
Copy Link

@Rogerddit commented on GitHub (Feb 11, 2026):

works with last bitwarden android app update 2026.1.1

<!-- gh-comment-id:3883910052 --> @Rogerddit commented on GitHub (Feb 11, 2026): works with last bitwarden android app update 2026.1.1
GiteaMirror commented 2026-05-01 12:35:26 -05:00
Author
Owner
Copy Link

@aj-rosado commented on GitHub (Mar 9, 2026):

WhatsApp has updated the Assetlinks file and this is now working as expected.
Thank you all for your patience.

<!-- gh-comment-id:4024073285 --> @aj-rosado commented on GitHub (Mar 9, 2026): WhatsApp has updated the Assetlinks file and this is now working as expected. Thank you all for your patience.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
app:authenticator
app:password-manager
bug
bug-passkey
customer-support
duplicate
enhancement
good first issue
help wanted
needs-reply
needs-response
pull-request
Mirrored from GitHub Pull Request
 question
No Label app:password-manager bug bug-passkey
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#50334
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?