github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-03-14 06:04:20 -05:00
Code Issues 144 Packages Projects Releases 116 Wiki Activity

Unknown error with FIDO and security key on Android #1348

New Issue
Closed
opened 2025-11-26 22:45:44 -06:00 by GiteaMirror · 21 comments
GiteaMirror commented 2025-11-26 22:45:44 -06:00
Owner
Copy Link

Originally created by @Raul6469 on GitHub (Sep 24, 2021).

Originally assigned to: @mpbw2 on GitHub.

Steps To Reproduce

Prerequisites: have a security key setup on the account (I have a Yubico Security Key)

  1. Login through the Android app with username and password
  2. The mobile browser opens automatically, tap "Authenticate WebAuthn"
  3. Use NFC to detect the security key

Expected Result

You get redirected to the app, and login is successful

Actual Result

I get redirected to the app, but still on the "FIDO2 WebAuth" screen, and I get an alert "An error occured". I can retry, but the bug still persists

Screenshots or Videos

No response

Additional Context

I had my YubiKey "migrated from FIDO", maybe that's some relevant information?
My issue reproduces on Firefox and Chrome

Operating System

Android

Operating System Version

7.1.1

Device

Samsung Galaxy J5 2016

Build Version

2.13.0

Beta

  • Using a pre-release version of the application.
Originally created by @Raul6469 on GitHub (Sep 24, 2021). Originally assigned to: @mpbw2 on GitHub. ### Steps To Reproduce Prerequisites: have a security key setup on the account (I have a Yubico Security Key) 1. Login through the Android app with username and password 2. The mobile browser opens automatically, tap "Authenticate WebAuthn" 3. Use NFC to detect the security key ### Expected Result You get redirected to the app, and login is successful ### Actual Result I get redirected to the app, but still on the "FIDO2 WebAuth" screen, and I get an alert "An error occured". I can retry, but the bug still persists ### Screenshots or Videos _No response_ ### Additional Context I had my YubiKey "migrated from FIDO", maybe that's some relevant information? My issue reproduces on Firefox and Chrome ### Operating System Android ### Operating System Version 7.1.1 ### Device Samsung Galaxy J5 2016 ### Build Version 2.13.0 ### Beta - [ ] Using a pre-release version of the application.
GiteaMirror added the bug label 2025-11-26 22:45:44 -06:00
GiteaMirror commented 2025-11-26 22:45:45 -06:00
Author
Owner
Copy Link

@mpbw2 commented on GitHub (Sep 24, 2021):

Hi @Raul6469 , we just started seeing this on another device in-house. We also discovered the same error was returned when using the key outside of the app, using the mobile browser to login to the web vault. Can you check if that happens for you as well?

@mpbw2 commented on GitHub (Sep 24, 2021): Hi @Raul6469 , we just started seeing this on another device in-house. We also discovered the same error was returned when using the key outside of the app, using the mobile browser to login to the web vault. Can you check if that happens for you as well?
GiteaMirror commented 2025-11-26 22:45:45 -06:00
Author
Owner
Copy Link

@Raul6469 commented on GitHub (Sep 25, 2021):

Hi @mportune-bw, I checked and I don't get an error. Instead, it continuously asks for the Yubikey. When I scan it, it immediately reopens the Android prompt for the security key, without logging me in. Is it the same behaviour for you? (I tested on Chrome and Firefox)

@Raul6469 commented on GitHub (Sep 25, 2021): Hi @mportune-bw, I checked and I don't get an error. Instead, it continuously asks for the Yubikey. When I scan it, it immediately reopens the Android prompt for the security key, without logging me in. Is it the same behaviour for you? (I tested on Chrome and Firefox)
GiteaMirror commented 2025-11-26 22:45:46 -06:00
Author
Owner
Copy Link

@mpbw2 commented on GitHub (Sep 27, 2021):

@Raul6469 Thanks for the confirmation - that's exactly what we're seeing too. It seems like some devices don't like the migration key for some reason. If you re-add the key everything should work properly. (You can add the key before deleting the migrated key so you won't have any gaps in 2FA coverage). Let me know if that works.

@mpbw2 commented on GitHub (Sep 27, 2021): @Raul6469 Thanks for the confirmation - that's exactly what we're seeing too. It seems like some devices don't like the migration key for some reason. If you re-add the key everything should work properly. (You can add the key _before_ deleting the migrated key so you won't have any gaps in 2FA coverage). Let me know if that works.
GiteaMirror commented 2025-11-26 22:45:46 -06:00
Author
Owner
Copy Link

@schlidel commented on GitHub (Sep 27, 2021):

Just want to report that I'm having similar issues with Yubikey 5c using USB. I've confirmed with other users on Reddit and Bitwarden Community they are having the same "authentication loop" problem.

For us when using Yubikey USB C after tapping "Use security key with USB" in the Google prompts if we don't immediately tap the gold plate on Yubikey we are pushed back to the blue button "Authenticate WebAuthn" page.

This loop will happen indefinitely if you don't tap the Yubikey plate quick enough.

I've removed all Yubikeys from BitWarden and re-added. Problem persists.

@schlidel commented on GitHub (Sep 27, 2021): Just want to report that I'm having similar issues with Yubikey 5c using USB. I've confirmed with other users on [Reddit ](https://www.reddit.com/r/Bitwarden/comments/pw6v29/yubikey_fido2_webauthn_on_android_it_works_but) and [Bitwarden Community](https://community.bitwarden.com/t/webauthn-fido-authentication-glitch-with-latest-android-app-update/33807) they are having the same "authentication loop" problem. For us when using Yubikey USB C after tapping "Use security key with USB" in the Google prompts if we don't immediately tap the gold plate on Yubikey we are pushed back to the blue button "Authenticate WebAuthn" page. This loop will happen indefinitely if you don't tap the Yubikey plate quick enough. I've removed all Yubikeys from BitWarden and re-added. Problem persists.
GiteaMirror commented 2025-11-26 22:45:47 -06:00
Author
Owner
Copy Link

@mpbw2 commented on GitHub (Sep 27, 2021):

@schlidel Thanks for the links to the discussions, lots of good info there. The problem you're experiencing seems to be between the browser and its implementation with Google Play Services (which I believe you mentioned you're already aware).

Just FYI you don't have to select the interface type (NFC/USB) when presented with the options. You can just tap or insert/tap and the system will figure it out. I don't experience the same issue with USB that you describe, but perhaps you can bypass it by not selecting USB before inserting the key? Let me know if that changes the behavior for you. If not, it might be worth making sure you're running the latest [everything], including Google Play Services.

@mpbw2 commented on GitHub (Sep 27, 2021): @schlidel Thanks for the links to the discussions, lots of good info there. The problem you're experiencing seems to be between the browser and its implementation with Google Play Services (which I believe you mentioned you're already aware). Just FYI you don't have to select the interface type (NFC/USB) when presented with the options. You can just tap or insert/tap and the system will figure it out. I don't experience the same issue with USB that you describe, but perhaps you can bypass it by _not_ selecting USB before inserting the key? Let me know if that changes the behavior for you. If not, it might be worth making sure you're running the latest [everything], including Google Play Services.
GiteaMirror commented 2025-11-26 22:45:47 -06:00
Author
Owner
Copy Link

@schlidel commented on GitHub (Sep 27, 2021):

@mportune-bw

If I don't select interface type and just tap Yubikey plate I'm prompted about turning Bluetooth on. I have Yubikey 5c so no Bluetooth or NFC. I think Yubikey is attempting to enter Yubico OTP at that point and it's just registering the return key and Bluetooth is the first of the options. I could try disabling Yubico OTP interface and see if that works but that wouldn't be a long time solution for me.

When I select "Use security key with USB" my Yubikey starts rapidly flashing awaiting my input. Before I select interface type it's probably still in keyboard mode.

I must tap use USB and then immediately tap YubiKey. It's the only way for me to get it to work.

Google Play Services: 21.36.14
Chrome: 93.0.4577.82

@schlidel commented on GitHub (Sep 27, 2021): @mportune-bw If I don't select interface type and just tap Yubikey plate I'm prompted about turning Bluetooth on. I have Yubikey 5c so no Bluetooth or NFC. I think Yubikey is attempting to enter Yubico OTP at that point and it's just registering the return key and Bluetooth is the first of the options. I could try disabling Yubico OTP interface and see if that works but that wouldn't be a long time solution for me. When I select "Use security key with USB" my Yubikey starts rapidly flashing awaiting my input. Before I select interface type it's probably still in keyboard mode. I must tap use USB and then immediately tap YubiKey. It's the only way for me to get it to work. Google Play Services: 21.36.14 Chrome: 93.0.4577.82
GiteaMirror commented 2025-11-26 22:45:47 -06:00
Author
Owner
Copy Link

@Raul6469 commented on GitHub (Sep 28, 2021):

@mportune-bw Re-adding the key into my account worked perfectly, thank you! 👍

@Raul6469 commented on GitHub (Sep 28, 2021): @mportune-bw Re-adding the key into my account worked perfectly, thank you! 👍
GiteaMirror commented 2025-11-26 22:45:48 -06:00
Author
Owner
Copy Link

@schlidel commented on GitHub (Sep 28, 2021):

@mportune-bw

I'm now able to tap on my Yubikey without pre-selecting the interface option (BT, NFC, etc) as you suggested by waiting to insert my Yubikey until after I've tapped "get started." If my key is already inserted when I tap "get started" the previous mentioned comment from above occurs and the Yubikey is treated as a keyboard until I make the USB selection.

This non selection method makes even it more difficult to log in however. I actually wasn't able to login that way. The method that works consistently well is to plug the Yubikey before tapping Authenticate WebAuthn and then be prepared to go through the authentication steps as fast as possible. If I take my time it never authenticates. Always back to the blue Authenticate WebAuthn page.

Is there a short timeout between hitting "Authenticate WebAuthn" and entering my FIDO credentials that I seem to be in a race against? If I can click Authenticate WebAuthn, Get Started, Use USB security key, and finally tap Yubikey in under 4-5 seconds it works perfect everytime.

Edit: I've actually practiced enough times logging in it doesnt even seem an issue any longer. But if I take a more casual/normal pace it still loops or times out. Newer users will run into this just slowing down enough to read the prompts.

@schlidel commented on GitHub (Sep 28, 2021): @mportune-bw I'm now able to tap on my Yubikey without pre-selecting the interface option (BT, NFC, etc) as you suggested by waiting to insert my Yubikey until after I've tapped "get started." If my key is already inserted when I tap "get started" the previous mentioned comment from above occurs and the Yubikey is treated as a keyboard until I make the USB selection. This non selection method makes even it more difficult to log in however. I actually wasn't able to login that way. The method that works consistently well is to plug the Yubikey before tapping Authenticate WebAuthn and then be prepared to go through the authentication steps as fast as possible. If I take my time it never authenticates. Always back to the blue Authenticate WebAuthn page. Is there a short timeout between hitting "Authenticate WebAuthn" and entering my FIDO credentials that I seem to be in a race against? If I can click Authenticate WebAuthn, Get Started, Use USB security key, and finally tap Yubikey in under 4-5 seconds it works perfect everytime. Edit: I've actually practiced enough times logging in it doesnt even seem an issue any longer. But if I take a more casual/normal pace it still loops or times out. Newer users will run into this just slowing down enough to read the prompts.
GiteaMirror commented 2025-11-26 22:45:48 -06:00
Author
Owner
Copy Link

@mpbw2 commented on GitHub (Sep 28, 2021):

Is there a short timeout between hitting "Authenticate WebAuthn" and entering my FIDO credentials that I seem to be in a race against?

It sure sounds like it, though it's not intentional and I'm not sure why we don't see the same thing. On my test devices I have a good 30 seconds to take action before it times out.

Does your key have a modified configuration or is it still factory-fresh? I'm thinking maybe the key is sending a character immediately upon activation that is canceling the process before you have time to touch the contact. (I don't know if that's even a thing, but your description makes me think of a HID keyboard sending an unexpected event) For reference I'm using a 5C NFC and the only customization is disabling OTP on the NFC channel per our help docs.

@mpbw2 commented on GitHub (Sep 28, 2021): > Is there a short timeout between hitting "Authenticate WebAuthn" and entering my FIDO credentials that I seem to be in a race against? It sure sounds like it, though it's not intentional and I'm not sure why we don't see the same thing. On my test devices I have a good 30 seconds to take action before it times out. Does your key have a modified configuration or is it still factory-fresh? I'm thinking maybe the key is sending a character immediately upon activation that is canceling the process before you have time to touch the contact. (I don't know if that's even a thing, but your description makes me think of a HID keyboard sending an unexpected event) For reference I'm using a 5C NFC and the only customization is disabling OTP on the NFC channel per our help docs.
GiteaMirror commented 2025-11-26 22:45:48 -06:00
Author
Owner
Copy Link

@schlidel commented on GitHub (Sep 28, 2021):

I attempted disabling OTP interface to see if that fixed it. It was one of the earlier suggestions from someone on Reddit.

Curiously, someone posted the new BitWarden blog article about mobile FIDO 2 support today and the screenshot of the WebAuthn page does not look like mine.

In the screenshot there is remember me, cancel, continue, and use another two-step login method below the blue WebAuthn button.

For me, all I have is the blue WebAuthn button. Is that normal?

Here is mine:

Screenshot_20210928-133725

And this is what's in the blog article:

POST_Product_Sept_2021_FIDO2_Security-Key

@schlidel commented on GitHub (Sep 28, 2021): I attempted disabling OTP interface to see if that fixed it. It was one of the earlier suggestions from someone on Reddit. Curiously, someone posted the new BitWarden [blog article](https://bitwarden.com/blog/fido2-security-key-support-enabled-for-mobile-clients/) about mobile FIDO 2 support today and the [screenshot](https://images.contentful.com/7rncvj1f8mw7/RAM5grVK4F0h1IiwUV1DM/157957d49d8f0bddec89b13e33607ff5/POST_Product_Sept_2021_FIDO2_Security-Key.png) of the WebAuthn page does not look like mine. In the screenshot there is remember me, cancel, continue, and use another two-step login method below the blue WebAuthn button. For me, all I have is the blue WebAuthn button. Is that normal? Here is mine: ![Screenshot_20210928-133725](https://user-images.githubusercontent.com/91495729/135146130-e4cfd021-0944-4354-92a7-443c28174832.png) And this is what's in the blog article: ![POST_Product_Sept_2021_FIDO2_Security-Key](https://user-images.githubusercontent.com/91495729/135146386-bbbf1e9b-15c2-49fd-8d72-1d8f0a81983c.png)
GiteaMirror commented 2025-11-26 22:45:48 -06:00
Author
Owner
Copy Link

@mpbw2 commented on GitHub (Sep 28, 2021):

I attempted disabling OTP interface to see if that fixed it. It was one of the earlier suggestions from someone on Reddit.

Is that the only customization on your key?

all I have is the blue WebAuthn button. Is that normal?

That's normal; the article screenshot is from the web vault. For mobile, the other controls are in the app, while only the auth button is used to start the webauthn flow.

@mpbw2 commented on GitHub (Sep 28, 2021): > I attempted disabling OTP interface to see if that fixed it. It was one of the earlier suggestions from someone on Reddit. Is that the only customization on your key? > all I have is the blue WebAuthn button. Is that normal? That's normal; the article screenshot is from the web vault. For mobile, the other controls are in the app, while only the auth button is used to start the webauthn flow.
GiteaMirror commented 2025-11-26 22:45:49 -06:00
Author
Owner
Copy Link

@schlidel commented on GitHub (Sep 28, 2021):

Ok, I apologize, it's not clear it's the web vault in the article because it is titled, "FIDO2 Security Key Support Enabled for Mobile Clients" and it seems to be published in response to the newly updated mobile clients.

I do see "remember me" and use "alternative 2FA options" in the interstitial app screen. So all functionality appears to be present.

I use static password in slot 2, but disabling OTP interface disables that as well. And while disabled the USB authentication loop problem is persistent.

Honestly, I'm no longer really worried about it. It functions well enough so I'll stop bugging you about it.

Thank you for developing this great service.

@schlidel commented on GitHub (Sep 28, 2021): Ok, I apologize, it's not clear it's the web vault in the article because it is titled, "FIDO2 Security Key Support Enabled for Mobile Clients" and it seems to be published in response to the newly updated mobile clients. I do see "remember me" and use "alternative 2FA options" in the interstitial app screen. So all functionality appears to be present. I use static password in slot 2, but disabling OTP interface disables that as well. And while disabled the USB authentication loop problem is persistent. Honestly, I'm no longer really worried about it. It functions well enough so I'll stop bugging you about it. Thank you for developing this great service.
GiteaMirror commented 2025-11-26 22:45:49 -06:00
Author
Owner
Copy Link

@tgreer-bw commented on GitHub (Oct 6, 2021):

@mportune-bw we may want to leave this open if possible, seems others may still have issues:

https://community.bitwarden.com/t/webauthn-fido-authentication-glitch-with-latest-android-app-update/33807/5

@tgreer-bw commented on GitHub (Oct 6, 2021): @mportune-bw we may want to leave this open if possible, seems others may still have issues: https://community.bitwarden.com/t/webauthn-fido-authentication-glitch-with-latest-android-app-update/33807/5
GiteaMirror commented 2025-11-26 22:45:49 -06:00
Author
Owner
Copy Link

@mpbw2 commented on GitHub (Oct 8, 2021):

I've managed to reproduce this on one of my test devices, though not consistently. In the failure cases, the browser is showing Navigation blocked in the debug console after successful hardware key validation. Some preliminary research confirms it is indeed a timing issue with user interaction. Some context: This is why the web-based Authenticate WebAuthn button is required (to prove that a human started the process). After some time has passed, that button press no longer "counts", and the browser blocks the javascript-based navigation needed to return to the app. As to why the timing seems to be inconsistent, I haven't a clue.

The only consistent workaround I'm seeing is adding a subsequent page to web connector flow containing a button a human can press if the javascript-based navigation fails. Here's an example referenced by others encountering the same issue: https://appauth.demo-app.io/oauth2redirect

I'll give that a whirl and keep this issue updated.

@mpbw2 commented on GitHub (Oct 8, 2021): I've managed to reproduce this on one of my test devices, though not consistently. In the failure cases, the browser is showing `Navigation blocked` in the debug console after successful hardware key validation. Some preliminary research confirms it is indeed a timing issue with user interaction. Some context: This is why the web-based `Authenticate WebAuthn` button is required (to prove that a human started the process). After some time has passed, that button press no longer "counts", and the browser blocks the javascript-based navigation needed to return to the app. As to why the timing seems to be inconsistent, I haven't a clue. The only consistent workaround I'm seeing is adding a subsequent page to web connector flow containing a button a human can press if the javascript-based navigation fails. Here's an example referenced by others encountering the same issue: https://appauth.demo-app.io/oauth2redirect I'll give that a whirl and keep this issue updated.
GiteaMirror commented 2025-11-26 22:45:50 -06:00
Author
Owner
Copy Link

@yourfishes commented on GitHub (May 16, 2022):

Hi,
I have this issue now.

Phone: Samsung S22
Android version: 12

  1. Enter username and password
  2. Phone automaticly opens Bitwarden WebAuthn site
  3. Click "Authenticate WebAuthn"
  4. Promted by google to "Get started"
  5. Choose option "Use security key with NFC"
  6. Scan key
  7. Choose option "Return to app"
  8. In bitwarden i get "An error has occured"

I have tried to reinstall the app, re-add the yubikey and all different browsers with the same result.
If I try the login on my old samsung s21, I have no issues with the login. The login also works perfect in web vault.

@yourfishes commented on GitHub (May 16, 2022): Hi, I have this issue now. Phone: Samsung S22 Android version: 12 1. Enter username and password 2. Phone automaticly opens Bitwarden WebAuthn site 3. Click "Authenticate WebAuthn" 4. Promted by google to "Get started" 5. Choose option "Use security key with NFC" 6. Scan key 7. Choose option "Return to app" 8. In bitwarden i get "An error has occured" I have tried to reinstall the app, re-add the yubikey and all different browsers with the same result. If I try the login on my old samsung s21, I have no issues with the login. The login also works perfect in web vault.
GiteaMirror commented 2025-11-26 22:45:50 -06:00
Author
Owner
Copy Link

@figadore commented on GitHub (Jun 9, 2022):

Same problem on my Pixel 6, in both the browser and Bitwarden app
I've tried doing the process quickly, but no luck. It looks like a loop with no errors at first, but when you go 'back' when the loop starts over, you see some errors
Screenshot_20220609-155435

The symptoms seem the same as above, but since the original issue was closed as fixed, should I create a new issue?

Edit: I had to remove the webauthn key that had the "migrated from FIDO" text and re-add it

@figadore commented on GitHub (Jun 9, 2022): ~Same problem on my Pixel 6, in both the browser and Bitwarden app~ ~I've tried doing the process quickly, but no luck. It looks like a loop with no errors at first, but when you go 'back' when the loop starts over, you see some errors~ ![Screenshot_20220609-155435](https://user-images.githubusercontent.com/3253971/172959447-1eb3b2fe-3177-416b-96ac-40684553d3be.png) ~The symptoms seem the same as above, but since the original issue was closed as fixed, should I create a new issue?~ Edit: I had to remove the webauthn key that had the "migrated from FIDO" text and re-add it
GiteaMirror commented 2025-11-26 22:45:50 -06:00
Author
Owner
Copy Link

@ImprovingRigmarole commented on GitHub (Jul 30, 2022):

Hi,
I'm recently switched to using webauthn,
and I'm experiencing the exact same on Android 12, Samsung A71.
I'm having the exact same flow of things and errors as https://github.com/bitwarden/mobile/issues/1548#issuecomment-1128076636 and https://github.com/bitwarden/mobile/issues/1548#issuecomment-1151700348.

I also tried many browsers on android, and it always comes back to this An unexpected error has occured. when using NFC.
Concerning USB, it seems that the Google Play Services prompt actually never tries to read the key, the led blinks really fast for about 1s, and whatever timing I press the button, it always stays stuck on the push the button now screen...

I also tried on https://webauthn.io/ which gives the exact same errors, so it might be caused by Google Play Services thing on Android 12...

@ImprovingRigmarole commented on GitHub (Jul 30, 2022): Hi, I'm recently switched to using webauthn, and I'm experiencing the exact same on Android 12, Samsung A71. I'm having the exact same flow of things and errors as https://github.com/bitwarden/mobile/issues/1548#issuecomment-1128076636 and https://github.com/bitwarden/mobile/issues/1548#issuecomment-1151700348. I also tried many browsers on android, and it always comes back to this `An unexpected error has occured.` when using NFC. Concerning USB, it seems that the Google Play Services prompt actually never tries to read the key, the led blinks really fast for about 1s, and whatever timing I press the button, it always stays stuck on the *push the button now* screen... I also tried on https://webauthn.io/ which gives the exact same errors, so it might be caused by Google Play Services thing on Android 12...
GiteaMirror commented 2025-11-26 22:45:50 -06:00
Author
Owner
Copy Link

@LeonNamowitz commented on GitHub (Sep 21, 2022):

Hey,
I'm having excatly the same problem on my Galaxy S10 running Android 10.
https://webauthn.io/ spits out errors as well here..

@LeonNamowitz commented on GitHub (Sep 21, 2022): Hey, I'm having excatly the same problem on my Galaxy S10 running Android 10. https://webauthn.io/ spits out errors as well here..
GiteaMirror commented 2025-11-26 22:45:50 -06:00
Author
Owner
Copy Link

@rayone commented on GitHub (Sep 29, 2022):

I have the exact same environment and issues as yourfishes commented on 17 May

Is there a work around?

@rayone commented on GitHub (Sep 29, 2022): I have the exact same environment and issues as [yourfishes](https://github.com/yourfishes) commented [on 17 May](https://github.com/bitwarden/mobile/issues/1548#issuecomment-1128076636) Is there a work around?
GiteaMirror commented 2025-11-26 22:45:51 -06:00
Author
Owner
Copy Link

@andmalc commented on GitHub (Oct 4, 2022):

The solution posted earlier in this thread removing and readding keys marked "migrated from FIDO" worked for me.

@andmalc commented on GitHub (Oct 4, 2022): The solution posted earlier in this thread removing and readding keys marked "migrated from FIDO" worked for me.
GiteaMirror commented 2025-11-26 22:45:51 -06:00
Author
Owner
Copy Link

@Mag1cByt3s commented on GitHub (Nov 22, 2022):

Since today i have the same issue on my oneplus 8 pro running android 12.

I am running vaultwarden on my local server tho.

I have no idea why this is happening or how to fix it. It only seems to affect my smartphone. On the computer everything works as expected.

@Mag1cByt3s commented on GitHub (Nov 22, 2022): Since today i have the same issue on my oneplus 8 pro running android 12. I am running vaultwarden on my local server tho. I have no idea why this is happening or how to fix it. It only seems to affect my smartphone. On the computer everything works as expected.
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 bug
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#1348
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?