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

[GH-ISSUE #6463] [PM-31597] Passkeys stopped working on some browsers (beginning with Android app 2026.1.0) #39419

New Issue
Closed
opened 2026-04-23 18:17:41 -05:00 by GiteaMirror · 26 comments
GiteaMirror commented 2026-04-23 18:17:41 -05:00
Owner
Copy Link

Originally created by @pamperer562580892423 on GitHub (Feb 2, 2026).
Original GitHub issue: https://github.com/bitwarden/android/issues/6463

Origin

Web (Browser)

Web URL or App name

https://community.bitwarden.com

Passkey Action

  • Creating new passkey (Registration)
  • Signing in (Authentication)

Build Information

© Bitwarden Inc. 2015-2026

Version: 2026.1.0 (21141)
📱 Fairphone FP5 🤖 15@35 📦 prod
🧱 commit: bitwarden/android/release/2026.1-rc42@67f83e3020b53f8d41e63a7d8f6bdb759ccb9ddc
💻 build source: bitwarden/android/actions/runs/21299199924/attempts/1
🦀 SDK: 2.0.0-4441-c5a3b833
🌩 Server: 2026.1.0 @ EU

Additional Information

Most important thing first: it seems to be connected to certain browsers! In my case, I get those errors only when I use Ironfox (which is in the list of the "privileged apps") - and not on Brave, Vivaldi, Firefox, Edge (those were the ones I tested it now).

And then for context, this issue was first reported here, but as you can see in the latest posts there, it doesn't seem to be an issue connected to the server (and also not to custom ROMs, as discussed there), as I could reproduce this issue with a BW EU cloud account, a stock ROM on my FP5, and the only meaningful difference seems to be the browser. (in that other GitHub issue, Fennec and Cromite were also mentioned where it wouldn't work)

[PS: IronFox 147.0.2, installed etc. via "Accrescent"]

When I try to create a passkey with Ironfox, I get this error (besides "An error has occurred. - Passkeys not supported for this app"):

Image

 

Furthermore, when I try to log in with an existing passkey via Ironfox, I get those error messages (again, besides "An error has occurred. - Passkeys not supported for this app"):

Image Image

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 @pamperer562580892423 on GitHub (Feb 2, 2026). Original GitHub issue: https://github.com/bitwarden/android/issues/6463 ### Origin Web (Browser) ### Web URL or App name https://community.bitwarden.com ### Passkey Action - [x] Creating new passkey (Registration) - [x] Signing in (Authentication) ### Build Information © Bitwarden Inc. 2015-2026 Version: 2026.1.0 (21141) 📱 Fairphone FP5 🤖 15@35 📦 prod 🧱 commit: bitwarden/android/release/2026.1-rc42@67f83e3020b53f8d41e63a7d8f6bdb759ccb9ddc 💻 build source: bitwarden/android/actions/runs/21299199924/attempts/1 🦀 SDK: 2.0.0-4441-c5a3b833 🌩 Server: 2026.1.0 @ EU ### Additional Information Most important thing first: it seems to be connected to certain browsers! In my case, I get those errors only when I use Ironfox (which is in the list of the "privileged apps") - and **not** on Brave, Vivaldi, Firefox, Edge (those were the ones I tested it now). And then for context, this issue was first reported [here](https://github.com/bitwarden/android/issues/6443), but as you can see in the latest posts there, it doesn't seem to be an issue connected to the server (and also not to custom ROMs, as discussed there), **as I could reproduce this issue with a BW EU cloud account, a stock ROM on my FP5, and the only meaningful difference seems to be the browser.** (in that other GitHub issue, Fennec and Cromite were also mentioned where it wouldn't work) [PS: IronFox 147.0.2, installed etc. via "Accrescent"] --- **When I try to create a passkey with Ironfox**, I get this error (besides "An error has occurred. - Passkeys not supported for this app"): <img width="500" height="1103" alt="Image" src="https://github.com/user-attachments/assets/571681d6-79be-42ee-b9bd-3d9c983ded7a" /> &nbsp; Furthermore, **when I try to log in with an existing passkey via Ironfox**, I get those error messages (again, besides "An error has occurred. - Passkeys not supported for this app"): <img width="500" height="1103" alt="Image" src="https://github.com/user-attachments/assets/027728aa-badf-4879-8973-3c184ca65459" /> <img width="500" height="1103" alt="Image" src="https://github.com/user-attachments/assets/a7dd4797-6fdb-4b48-9e84-9b8172bdaf4f" /> ### 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 bug-passkeyapp:password-manager labels 2026-04-23 18:17:42 -05:00
GiteaMirror commented 2026-04-23 18:17:45 -05:00
Author
Owner
Copy Link

@bitwarden-bot commented on GitHub (Feb 2, 2026):

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

<!-- gh-comment-id:3835174765 --> @bitwarden-bot commented on GitHub (Feb 2, 2026): Thank you for your report! We've added this to our internal board for review. ID: [PM-31597](https://bitwarden.atlassian.net/browse/PM-31597) [PM-31597]: https://bitwarden.atlassian.net/browse/PM-31597?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ
GiteaMirror commented 2026-04-23 18:17:46 -05:00
Author
Owner
Copy Link

@jtodddd commented on GitHub (Feb 3, 2026):

Hi there,

This has been escalated for further investigation. If you have more information that can help us, please add it below.

Thanks!

<!-- gh-comment-id:3841557104 --> @jtodddd commented on GitHub (Feb 3, 2026): Hi there, This has been escalated for further investigation. If you have more information that can help us, please add it below. Thanks!
GiteaMirror commented 2026-04-23 18:17:48 -05:00
Author
Owner
Copy Link

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

@jtodddd I think I would only like to emphasize the following (again):

  • I don't experience this issue on Brave, Vivaldi, Firefox and Edge (the only other browsers where I tested it now explicitly)
  • I do experience this issue with IronFox - and others reported here at least to experience the issue also with "Fennec" and "Cromite" (I don't know which other browsers might also be affected)
  • in that other GitHub issue, it was also reported that downgrading the Android app to 2025.12.1 or lower would resolve the issue on these browsers again - so it looks like it must be a change with Android app version 2026.1.0 that's causing this
<!-- gh-comment-id:3849482947 --> @pamperer562580892423 commented on GitHub (Feb 4, 2026): @jtodddd I think I would only like to emphasize the following (again): - I **don't** experience this issue on Brave, Vivaldi, Firefox and Edge (the only other browsers where I tested it now explicitly) - I **do** experience this issue with IronFox - and others reported [here](https://github.com/bitwarden/android/issues/6443) at least to experience the issue also with "Fennec" and "Cromite" (I don't know which other browsers might also be affected) - in that other GitHub issue, it was also reported that downgrading the Android app to 2025.12.1 or lower would resolve the issue on these browsers again - so it looks like it must be a change with Android app version 2026.1.0 that's causing this
GiteaMirror commented 2026-04-23 18:17:49 -05:00
Author
Owner
Copy Link

@rjmidau commented on GitHub (Feb 5, 2026):

I'm experiencing the same "Passkeys not supported for this app" issue using Iceraven with Bitwarden 2026.1.0. Downgrading Bitwarden to 2025.12.1 fixes the issue.

<!-- gh-comment-id:3850615048 --> @rjmidau commented on GitHub (Feb 5, 2026): I'm experiencing the same "Passkeys not supported for this app" issue using [Iceraven](https://github.com/fork-maintainers/iceraven-browser) with Bitwarden 2026.1.0. Downgrading Bitwarden to 2025.12.1 fixes the issue.
GiteaMirror commented 2026-04-23 18:17:50 -05:00
Author
Owner
Copy Link

@Klax999 commented on GitHub (Feb 5, 2026):

Can confirm this is the case, including passkeys with Discord. > .

<!-- gh-comment-id:3850826798 --> @Klax999 commented on GitHub (Feb 5, 2026): Can confirm this is the case, including passkeys with Discord. > .
GiteaMirror commented 2026-04-23 18:17:51 -05:00
Author
Owner
Copy Link

@Klax999 commented on GitHub (Feb 5, 2026):

And passkeys are now working again for PayPal!

<!-- gh-comment-id:3850839819 --> @Klax999 commented on GitHub (Feb 5, 2026): And passkeys are now working again for PayPal!
GiteaMirror commented 2026-04-23 18:17:51 -05:00
Author
Owner
Copy Link

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

@Klax999:

And passkeys are now working again for PayPal!

That is a confusing info in an issue about browsers where passkeys don't work at all at the moment... or do you want to say that all other passkeys don't work in e.g. IronFox, but only the passkey for PayPal works now there?

<!-- gh-comment-id:3850902209 --> @pamperer562580892423 commented on GitHub (Feb 5, 2026): @Klax999: > And passkeys are now working again for PayPal! That is a confusing info in an issue about browsers where passkeys don't work at all at the moment... or do you want to say that all other passkeys don't work in e.g. IronFox, but only the passkey for PayPal works now there?
GiteaMirror commented 2026-04-23 18:17:52 -05:00
Author
Owner
Copy Link

@Klax999 commented on GitHub (Feb 5, 2026):

Sorry. Let me be more specific. When I downgraded from 2026.1 to 2025.12.1, passkeys worked again in IronFox. I tested this using MyGov. Additionally, the standalone applications Discord and PayPal, which also didn't work for the latest update, worked again for logging in using the passkey option, too.

<!-- gh-comment-id:3850909457 --> @Klax999 commented on GitHub (Feb 5, 2026): Sorry. Let me be more specific. When I downgraded from 2026.1 to 2025.12.1, passkeys worked again in IronFox. I tested this using MyGov. Additionally, the standalone applications Discord and PayPal, which also didn't work for the latest update, worked again for logging in using the passkey option, too.
GiteaMirror commented 2026-04-23 18:17:53 -05:00
Author
Owner
Copy Link

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

@Klax999 Thanks for clarifying that. And I'm honestly glad that those passkeys for PayPal and Discord work again with 2025.12.1 then - but on the other hand, it's not relevant for this issue here.

<!-- gh-comment-id:3850984980 --> @pamperer562580892423 commented on GitHub (Feb 5, 2026): @Klax999 Thanks for clarifying that. And I'm honestly glad that those passkeys for PayPal and Discord work again with 2025.12.1 then - but on the other hand, it's not relevant for this issue here.
GiteaMirror commented 2026-04-23 18:17:53 -05:00
Author
Owner
Copy Link

@ViZiD commented on GitHub (Feb 6, 2026):

I'm having the same problem with version 2026.1.0 of the Fennec browser, but everything works fine in Firefox.

<!-- gh-comment-id:3858840353 --> @ViZiD commented on GitHub (Feb 6, 2026): I'm having the same problem with version 2026.1.0 of the Fennec browser, but everything works fine in Firefox.
GiteaMirror commented 2026-04-23 18:17:54 -05:00
Author
Owner
Copy Link

@ToniCipriani commented on GitHub (Feb 6, 2026):

It's broken for apps as well. I cannot use my passkey stored in Bitwarden in the EQ Bank (same website works with that same passkey on Firefox desktop web extension), Aliexpress.

Only works if I downgrade back to 2025.12.1. Currently 2026.1.0 from Play Store.

<!-- gh-comment-id:3861032018 --> @ToniCipriani commented on GitHub (Feb 6, 2026): It's broken for apps as well. I cannot use my passkey stored in Bitwarden in the EQ Bank (same website works with that same passkey on Firefox desktop web extension), Aliexpress. Only works if I downgrade back to 2025.12.1. Currently 2026.1.0 from Play Store.
GiteaMirror commented 2026-04-23 18:17:55 -05:00
Author
Owner
Copy Link

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

@ToniCipriani:

It's broken for apps as well. I cannot use my passkey stored in Bitwarden in the EQ Bank (same website works with that same passkey on Firefox desktop web extension), Aliexpress.

Only works if I downgrade back to 2025.12.1. Currently 2026.1.0 from Play Store.

I think the "passkey issue" with Android app version 2026.1.0 and apps is currently tracked here: https://github.com/bitwarden/android/issues/6454

<!-- gh-comment-id:3861059882 --> @pamperer562580892423 commented on GitHub (Feb 6, 2026): @ToniCipriani: > It's broken for apps as well. I cannot use my passkey stored in Bitwarden in the EQ Bank (same website works with that same passkey on Firefox desktop web extension), Aliexpress. > > Only works if I downgrade back to 2025.12.1. Currently 2026.1.0 from Play Store. I think the "passkey issue" with Android app version 2026.1.0 and _apps_ is currently tracked here: https://github.com/bitwarden/android/issues/6454
GiteaMirror commented 2026-04-23 18:17:56 -05:00
Author
Owner
Copy Link

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

General info for all those who use Vivaldi browser on Android - and this now was/is not part of this GitHub issue here (since Vivaldi browser worked a few days ago as expected)...

But, Vivaldi mobile just released an update (to version 7.8), which makes it necessary to enable the following in the Vivaldi settings for it to continue to work with the Bitwarden app: go to "Autofill services", enable “Autofill using another service” there and allow Vivaldi to restart.

(this seems to work - for now?! - without enabling "autofill integration" for Vivaldi in the BW mobile app, which not even is there as an option at the moment...)

<!-- gh-comment-id:3865360442 --> @pamperer562580892423 commented on GitHub (Feb 7, 2026): **General info for all those who use Vivaldi browser on Android** - and this now was/is **not** part of this GitHub issue here (since Vivaldi browser worked a few days ago as expected)... But, Vivaldi mobile just released an update (to version 7.8), **which makes it necessary to enable the following in the Vivaldi settings for it to continue to work with the Bitwarden app:** go to "Autofill services", enable “Autofill using another service” there and allow Vivaldi to restart. (this seems to work - for now?! - without enabling "autofill integration" for Vivaldi in the BW mobile app, which not even is there as an option at the moment...)
GiteaMirror commented 2026-04-23 18:17:56 -05:00
Author
Owner
Copy Link

@nnnn20430 commented on GitHub (Feb 8, 2026):

2026.1.0 broke passkeys for me on every app that isn't Brave...
Fennec, Cromite, and crypto exchange apps like MEXC and Binance.
Bitwarden says "Passkeys not supported for this app"
Downgrading to 2025.12.1 makes everything work again.

<!-- gh-comment-id:3867499153 --> @nnnn20430 commented on GitHub (Feb 8, 2026): 2026.1.0 broke passkeys for me on every app that isn't Brave... Fennec, Cromite, and crypto exchange apps like MEXC and Binance. Bitwarden says "Passkeys not supported for this app" Downgrading to 2025.12.1 makes everything work again.
GiteaMirror commented 2026-04-23 18:17:57 -05:00
Author
Owner
Copy Link

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

@nnnn20430:

and crypto exchange apps like MEXC and Binance.

Passkey issues with Android apps are getting tracked here: https://github.com/bitwarden/android/issues/6454 (and there are first reports, that Android app 2026.1.1 might have fixed this already - but not the issue with some browser like Fennec, Cromite, IronFox...)

<!-- gh-comment-id:3868257451 --> @pamperer562580892423 commented on GitHub (Feb 8, 2026): @nnnn20430: > and crypto exchange apps like MEXC and Binance. Passkey issues with Android apps are getting tracked here: https://github.com/bitwarden/android/issues/6454 (and there are first reports, that Android app 2026.1.1 might have fixed _this_ already - but not the issue with some browser like Fennec, Cromite, IronFox...)
GiteaMirror commented 2026-04-23 18:17:58 -05:00
Author
Owner
Copy Link

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

2026.1.1 just arrived on my phone - but still the same errors with IronFox as reported in my original post.

<!-- gh-comment-id:3873282110 --> @pamperer562580892423 commented on GitHub (Feb 9, 2026): 2026.1.1 just arrived on my phone - but still the same errors with IronFox as reported in my original post.
GiteaMirror commented 2026-04-23 18:17:59 -05:00
Author
Owner
Copy Link

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

I'm experiencing the same "Passkeys not supported for this app" issue using Iceraven with Bitwarden 2026.1.0. Downgrading Bitwarden to 2025.12.1 fixes the issue.

I'm now also on 2026.1.1 and this issues still exists with Iceraven.

<!-- gh-comment-id:3875653160 --> @ASM88 commented on GitHub (Feb 10, 2026): > I'm experiencing the same "Passkeys not supported for this app" issue using [Iceraven](https://github.com/fork-maintainers/iceraven-browser) with Bitwarden 2026.1.0. Downgrading Bitwarden to 2025.12.1 fixes the issue. I'm now also on 2026.1.1 and this issues still exists with Iceraven.
GiteaMirror commented 2026-04-23 18:18:00 -05:00
Author
Owner
Copy Link

@KikMyaz commented on GitHub (Feb 15, 2026):

Passkey is still broken for Fennec (org.mozilla.fennec_fdroid, versionCode 1470220) as of Bitwarden 2026.1.1.

Honestly, horrified that such a basic feature keeps failing. Never ever had this issue on Proton Pass. Makes me wonder how they even perform the bare minimum tests/QAs on this app.

Cancelled subscription and moving back to Proton Pass for now until they get it back together.

<!-- gh-comment-id:3905019846 --> @KikMyaz commented on GitHub (Feb 15, 2026): Passkey is still broken for Fennec (org.mozilla.fennec_fdroid, versionCode 1470220) as of Bitwarden 2026.1.1. Honestly, horrified that such a basic feature keeps failing. Never ever had this issue on Proton Pass. Makes me wonder how they even perform the bare minimum tests/QAs on this app. Cancelled subscription and moving back to Proton Pass for now until they get it back together.
GiteaMirror commented 2026-04-23 18:18:01 -05:00
Author
Owner
Copy Link

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

@KikMyaz As you can see, the fix (https://github.com/bitwarden/android/pull/6502) was merged five days ago (Feb 10). Since 2026.1.1 was released 10 days ago (Feb 5), I don't see how that fix could have been included in 2026.1.1. - But I would expect a fix in the next release.

<!-- gh-comment-id:3905029918 --> @pamperer562580892423 commented on GitHub (Feb 15, 2026): @KikMyaz As you can see, the fix (https://github.com/bitwarden/android/pull/6502) was merged five days ago (Feb 10). Since [2026.1.1](https://github.com/bitwarden/android/releases/tag/v2026.1.1-bwpm) was released 10 days ago (Feb 5), I don't see how that fix could have been included in 2026.1.1. - But I would expect a fix in the next release.
GiteaMirror commented 2026-04-23 18:18:02 -05:00
Author
Owner
Copy Link

@KikMyaz commented on GitHub (Feb 15, 2026):

@KikMyaz As you can see, the fix (#6502) was merged five days ago (Feb 10). Since 2026.1.1 was released 10 days ago (Feb 5), I don't see how that fix could have been included in 2026.1.1. - But I would expect a fix in the next release.

I mean... the fact that it even took more than 5 days to fix a single comma is already bad

<!-- gh-comment-id:3905035038 --> @KikMyaz commented on GitHub (Feb 15, 2026): > [@KikMyaz](https://github.com/KikMyaz) As you can see, the fix ([#6502](https://github.com/bitwarden/android/pull/6502)) was merged five days ago (Feb 10). Since [2026.1.1](https://github.com/bitwarden/android/releases/tag/v2026.1.1-bwpm) was released 10 days ago (Feb 5), I don't see how that fix could have been included in 2026.1.1. - But I would expect a fix in the next release. I mean... the fact that it even took more than 5 days to fix a single comma is already bad
GiteaMirror commented 2026-04-23 18:18:03 -05:00
Author
Owner
Copy Link

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

@KikMyaz:

I mean... the fact that it even took more than 5 days to fix a single comma is already bad

So, eventually, you don't want them to test thing first but just rush the fix? - And I thought you wanted "bare minimum tests".

<!-- gh-comment-id:3905042388 --> @pamperer562580892423 commented on GitHub (Feb 15, 2026): @KikMyaz: > I mean... the fact that it even took more than 5 days to fix a single comma is already bad So, eventually, you don't want them to test thing first but just rush the fix? - And I thought you wanted "bare minimum tests".
GiteaMirror commented 2026-04-23 18:18:06 -05:00
Author
Owner
Copy Link

@KikMyaz commented on GitHub (Feb 15, 2026):

@KikMyaz:

I mean... the fact that it even took more than 5 days to fix a single comma is already bad

So, eventually, you don't want them to test thing first but just rush the fix? - And I thought you wanted "bare minimum tests".

Are you ragebaiting lol? It shouldn't even be an issue in the first place. Even vscode on default settings would prompt you the JSON isn't properly formatted if you left a comma there. You've got to not have coded in the past 5 years to even get yourself into that situation... plus let me remind you that it was working before, meaning it must have slipped past QA at least once

<!-- gh-comment-id:3905047197 --> @KikMyaz commented on GitHub (Feb 15, 2026): > [@KikMyaz](https://github.com/KikMyaz): > > > I mean... the fact that it even took more than 5 days to fix a single comma is already bad > > So, eventually, you don't want them to test thing first but just rush the fix? - And I thought you wanted "bare minimum tests". Are you ragebaiting lol? It shouldn't even be an issue in the first place. Even vscode on default settings would prompt you the JSON isn't properly formatted if you left a comma there. You've got to not have coded in the past 5 years to even get yourself into that situation... plus let me remind you that it *was* working before, meaning it must have slipped past QA at least once
GiteaMirror commented 2026-04-23 18:18:07 -05:00
Author
Owner
Copy Link

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

@KikMyaz:

It shouldn't even be an issue in the first place.

I agree. No bug should ever happen. - I still search for that piece of software. 😅

plus let me remind you that it was working before, meaning it must have slipped past QA at least once

Yeah, seems so. But you can't demand more time for QA and rant about fixes taking too long at the same time.

<!-- gh-comment-id:3905060043 --> @pamperer562580892423 commented on GitHub (Feb 15, 2026): @KikMyaz: > It shouldn't even be an issue in the first place. I agree. No bug should ever happen. - I still search for that piece of software. 😅 > plus let me remind you that it was working before, meaning it must have slipped past QA at least once Yeah, seems so. But you can't demand more time for QA and rant about fixes taking too long at the same time.
GiteaMirror commented 2026-04-23 18:18:07 -05:00
Author
Owner
Copy Link

@basnappl commented on GitHub (Feb 19, 2026):

This issue persists for me with the latest Android version (2026.2.0). Exactly as described in the original issue. Passkeys work with Chrome, but not IronFox, Cromite, or Fennec.

<!-- gh-comment-id:3930772364 --> @basnappl commented on GitHub (Feb 19, 2026): This issue persists for me with the latest Android version (2026.2.0). Exactly as described in the original issue. Passkeys work with Chrome, but not IronFox, Cromite, or Fennec.
GiteaMirror commented 2026-04-23 18:18:08 -05:00
Author
Owner
Copy Link

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

@basnappl I think this is expected. It seems the fix was merged on Feb 10, but Android version 2026.2.0 only includes PRs up to Feb 5. --> The fix didn't make it into 2026.2.0.

<!-- gh-comment-id:3930838267 --> @pamperer562580892423 commented on GitHub (Feb 20, 2026): @basnappl I think this is expected. It seems the [fix](https://github.com/bitwarden/android/pull/6502) was merged on Feb 10, [but Android version 2026.2.0 only includes PRs up to Feb 5.](https://github.com/bitwarden/android/compare/v2026.1.1-bwpm...v2026.2.0-bwpm) --> The fix didn't make it into 2026.2.0.
GiteaMirror commented 2026-04-23 18:18:09 -05:00
Author
Owner
Copy Link

@basnappl commented on GitHub (Feb 20, 2026):

@basnappl I think this is expected. It seems the fix was merged on Feb 10, but Android version 2026.2.0 only includes PRs up to Feb 5. --> The fix didn't make it into 2026.2.0.

OK, rad. Thanks for the clarification. I look forward to this being fixed in the next version!

<!-- gh-comment-id:3930845954 --> @basnappl commented on GitHub (Feb 20, 2026): > [@basnappl](https://github.com/basnappl) I think this is expected. It seems the [fix](https://github.com/bitwarden/android/pull/6502) was merged on Feb 10, [but Android version 2026.2.0 only includes PRs up to Feb 5.](https://github.com/bitwarden/android/compare/v2026.1.1-bwpm...v2026.2.0-bwpm) --> The fix didn't make it into 2026.2.0. OK, rad. Thanks for the clarification. I look forward to this being fixed in the next version!
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-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#39419
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?