github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-03-25 07:41:55 -05:00
Code Issues 144 Packages Projects Releases 118 Wiki Activity

iOS Autocomplete filles old/wrong password #1045

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

Originally created by @NPadrutt on GitHub (Jun 15, 2020).

Originally assigned to: @mpbw2 on GitHub.

Describe the Bug

I adjusted my Hotmail Password. The password got synced to my iPhone and iPad correctly, but when I autocomplete the password in any password field it fills the wrong one. When I copy and paste it manually it works.

Steps To Reproduce

This was how I did it. Not sure how consistent reproduceable that is

  1. Change Hotmail password
  2. Start bitwarden and ensure that it is synced
  3. Open app who uses Hotmail login and autofill password
  4. Notice that password was incorrect (in my case I could see it by that it was much shorter - or the "login failed message)
  5. Open bitwarden and copy the password
  6. switch back to the application and paste password
  7. Login successful

Expected Result

The correct password is filled with Autofill Password

Actual Result

It seems the old password is used in Autofill.

Screenshots or Videos

Environment

  • Device: [e.g. iPhone6]
    iPhone 11 Pro (iOS 13.5.1)
    iPad Pro 2020 (iOS 13.5.1)
  • Operating system: [e.g. iOS 8.1]
  • Build Version (go to "Settings" → "About" in the app): [e.g. 2.3.0 (2221)]: 2.4.3(69)
  • Is this a Beta release? [Y/N] N

Additional Context

Originally created by @NPadrutt on GitHub (Jun 15, 2020). Originally assigned to: @mpbw2 on GitHub. <!-- Comment: Please do not submit feature requests. The [Community Forums][1] has a section for submitting, voting for, and discussing product feature requests. [1]: https://community.bitwarden.com --> ## Describe the Bug I adjusted my Hotmail Password. The password got synced to my iPhone and iPad correctly, but when I autocomplete the password in any password field it fills the wrong one. When I copy and paste it manually it works. <!-- Comment: A clear and concise description of what the bug is. --> ## Steps To Reproduce <!-- Comment: How can we reproduce the behavior: --> This was how I did it. Not sure how consistent reproduceable that is 1. Change Hotmail password 2. Start bitwarden and ensure that it is synced 3. Open app who uses Hotmail login and autofill password 4. Notice that password was incorrect (in my case I could see it by that it was much shorter - or the "login failed message) 5. Open bitwarden and copy the password 6. switch back to the application and paste password 7. Login successful ## Expected Result The correct password is filled with Autofill Password <!-- Comment: A clear and concise description of what you expected to happen. --> ## Actual Result It seems the old password is used in Autofill. <!-- Comment: A clear and concise description of what is happening. --> ## Screenshots or Videos <!-- Comment: If applicable, add screenshots and/or a short video to help explain your problem. --> ## Environment - Device: [e.g. iPhone6] iPhone 11 Pro (iOS 13.5.1) iPad Pro 2020 (iOS 13.5.1) - Operating system: [e.g. iOS 8.1] - Build Version (go to "Settings" → "About" in the app): [e.g. 2.3.0 (2221)]: 2.4.3(69) - Is this a Beta release? [Y/N] N ## Additional Context <!-- Comment: Add any other context about the problem here. -->
GiteaMirror commented 2025-11-26 22:37:38 -06:00
Author
Owner
Copy Link

@dxyzx0 commented on GitHub (Jun 17, 2020):

Exact same issue. This issue happened after the latest update on iOS.

Environment

  • Device: [e.g. iPhone6]
    iPhone 7 plus
  • Operating system: iOS 12.0.0
  • Build Version (go to "Settings" → "About" in the app): 2.4.3(69)
  • Is this a Beta release? [Y/N] N
@dxyzx0 commented on GitHub (Jun 17, 2020): Exact same issue. This issue happened after the latest update on iOS. ## Environment * Device: [e.g. iPhone6] iPhone 7 plus * Operating system: iOS 12.0.0 * Build Version (go to "Settings" → "About" in the app): 2.4.3(69) * Is this a Beta release? [Y/N] N
GiteaMirror commented 2025-11-26 22:37:38 -06:00
Author
Owner
Copy Link

@clayadams5226 commented on GitHub (Jun 25, 2020):

@NPadrutt can you verify a couple of things for me:

  1. Can you verify keychain autofill is deactivated and Bitwarden is the only application with autofill permission?

  2. After you change your Hotmail password, are you first logging back into the Bitwarden application or going straight to the app extension/autofill service?

@clayadams5226 commented on GitHub (Jun 25, 2020): @NPadrutt can you verify a couple of things for me: 1. Can you verify keychain autofill is deactivated and Bitwarden is the only application with autofill permission? 2. After you change your Hotmail password, are you first logging back into the Bitwarden application or going straight to the app extension/autofill service?
GiteaMirror commented 2025-11-26 22:37:38 -06:00
Author
Owner
Copy Link

@NPadrutt commented on GitHub (Jun 25, 2020):

@clayadams5226

  1. that is the case
  2. I did first go to the app I wanted to login in the hope / anticipation that bitwarden will sync when it opens the list with the suggestions. After that wasn't the case I went to the bitwarden app and synced manually and checked that it was correct now. Then I went back to the app and tried a gain - which failed still. I also tried to cancel the authentication or restart the app in case anything was cached but both didn't work. Funny enough, as far as I can remember I tried even to restart my iPhone and it still did autofill it incorrect. Same on my iPad for that sake.
@NPadrutt commented on GitHub (Jun 25, 2020): @clayadams5226 1. that is the case 2. I did first go to the app I wanted to login in the hope / anticipation that bitwarden will sync when it opens the list with the suggestions. After that wasn't the case I went to the bitwarden app and synced manually and checked that it was correct now. Then I went back to the app and tried a gain - which failed still. I also tried to cancel the authentication or restart the app in case anything was cached but both didn't work. Funny enough, as far as I can remember I tried even to restart my iPhone and it still did autofill it incorrect. Same on my iPad for that sake.
GiteaMirror commented 2025-11-26 22:37:38 -06:00
Author
Owner
Copy Link

@brenr commented on GitHub (Jun 29, 2020):

Yep same sort of situation here. Autofill is showing old passwords despite me deleting them and syncing vault several times.

@brenr commented on GitHub (Jun 29, 2020): Yep same sort of situation here. Autofill is showing old passwords despite me deleting them and syncing vault several times.
GiteaMirror commented 2025-11-26 22:37:38 -06:00
Author
Owner
Copy Link

@HelmyBD2 commented on GitHub (Jul 4, 2020):

Same here! iPhone 7 with latest iOS and app version.

@HelmyBD2 commented on GitHub (Jul 4, 2020): Same here! iPhone 7 with latest iOS and app version.
GiteaMirror commented 2025-11-26 22:37:38 -06:00
Author
Owner
Copy Link

@clayadams5226 commented on GitHub (Jul 7, 2020):

As a work around, I've found that uninstalling the app and installing it again seems to resolve this issue.

@clayadams5226 commented on GitHub (Jul 7, 2020): As a work around, I've found that uninstalling the app and installing it again seems to resolve this issue.
GiteaMirror commented 2025-11-26 22:37:39 -06:00
Author
Owner
Copy Link

@HelmyBD2 commented on GitHub (Jul 7, 2020):

I tried that but problem persist

Sent from my iPhone

On 7 Jul 2020, at 10:24, Clayton notifications@github.com wrote:



As a work around, I've found that uninstalling the app and installing it again seems to resolve this issue.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/bitwarden/mobile/issues/980#issuecomment-654629220, or unsubscribehttps://github.com/notifications/unsubscribe-auth/APII77XMRYVXSSCX7H3YWTDR2K5SVANCNFSM4N54IXVA.

@HelmyBD2 commented on GitHub (Jul 7, 2020): I tried that but problem persist Sent from my iPhone On 7 Jul 2020, at 10:24, Clayton <notifications@github.com> wrote:  As a work around, I've found that uninstalling the app and installing it again seems to resolve this issue. — You are receiving this because you commented. Reply to this email directly, view it on GitHub<https://github.com/bitwarden/mobile/issues/980#issuecomment-654629220>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/APII77XMRYVXSSCX7H3YWTDR2K5SVANCNFSM4N54IXVA>.
GiteaMirror commented 2025-11-26 22:37:39 -06:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jul 9, 2020):

I have the same problem on my iPhone XR / iOS 13.5.1

Only way to make the new synced passwords show up is restart my phone.

@ghost commented on GitHub (Jul 9, 2020): I have the same problem on my iPhone XR / iOS 13.5.1 Only way to make the new synced passwords show up is restart my phone.
GiteaMirror commented 2025-11-26 22:37:39 -06:00
Author
Owner
Copy Link

@fL0n9 commented on GitHub (Jul 10, 2020):

I have the same problem on my iPhone 8 / iOS 13.5.1

@fL0n9 commented on GitHub (Jul 10, 2020): I have the same problem on my iPhone 8 / iOS 13.5.1
GiteaMirror commented 2025-11-26 22:37:40 -06:00
Author
Owner
Copy Link

@stub68 commented on GitHub (Jul 12, 2020):

Yes I have had the same issue on iPhone7 and latest iOS. I created an account and accepted the strong master password but when I try to log in using the password saved in iOS I receive a wrong password error from Bitwarden. I emailed support and have tried deleting the app and re-installing, but the problem persists. I understand the issue is being looked into.

@stub68 commented on GitHub (Jul 12, 2020): Yes I have had the same issue on iPhone7 and latest iOS. I created an account and accepted the strong master password but when I try to log in using the password saved in iOS I receive a wrong password error from Bitwarden. I emailed support and have tried deleting the app and re-installing, but the problem persists. I understand the issue is being looked into.
GiteaMirror commented 2025-11-26 22:37:40 -06:00
Author
Owner
Copy Link

@MattTheDev commented on GitHub (Jul 13, 2020):

@NPadrutt Hi there, Nino!

I'm working on fixing this issue for you. It's an odd one - I can get it to repro in some cases .. and not in others. A lot of the time, the resolution thats worked for me is:

  1. Close all browser instances
  2. Launch BW
  3. Sync
  4. Launch browser and restart the authentication process.

I thought I had a resolution - as seen above. But it wasn't the desired solution. I will keep you in the loop on this one. Let me know if the issue still persists as well. Thanks!

@MattTheDev commented on GitHub (Jul 13, 2020): @NPadrutt Hi there, Nino! I'm working on fixing this issue for you. It's an odd one - I can get it to repro in some cases .. and not in others. A lot of the time, the resolution thats worked for me is: 1. Close all browser instances 2. Launch BW 3. Sync 4. Launch browser and restart the authentication process. I thought I had a resolution - as seen above. But it wasn't the desired solution. I will keep you in the loop on this one. Let me know if the issue still persists as well. Thanks!
GiteaMirror commented 2025-11-26 22:37:40 -06:00
Author
Owner
Copy Link

@greybeard-code commented on GitHub (Jul 15, 2020):

Similar issue.
iOS 13.5.1 iPhone 8 Plus. Auto-fill password is Bitwarden only, but iCloud Keychain, KeePass Touch and Lass pass are installed.

Created new login entry on PC Firefox extension. Sync'd on PC. Sync'd on iPhone. Can search & find the entry in app, but not with keyboard auto-fill. Searching in the autofill can't locate the new entry by name.

Removed Keepass and Lasspass, rebooted phone. Now that entry is found.

@greybeard-code commented on GitHub (Jul 15, 2020): Similar issue. iOS 13.5.1 iPhone 8 Plus. Auto-fill password is Bitwarden only, but iCloud Keychain, KeePass Touch and Lass pass are installed. Created new login entry on PC Firefox extension. Sync'd on PC. Sync'd on iPhone. Can search & find the entry in app, but not with keyboard auto-fill. Searching in the autofill can't locate the new entry by name. Removed Keepass and Lasspass, rebooted phone. Now that entry is found.
GiteaMirror commented 2025-11-26 22:37:40 -06:00
Author
Owner
Copy Link

@IhanaOlli commented on GitHub (Jul 17, 2020):

Same issue here. iOS 13.6, iPhone 11 Pro Max, BW 2.5.0 (193).
I uninstalled & reinstalled BW and autofill still remembers incorrect data from earlier, before reinstallation!

I normally use Firefox on iOS and autofill using that shows old data. However, if I access same site with Safari and tap the 🔑 button on autofill bar and then "Bitwarden..." autofill data gets updated! So there is some kind of caching, maybe by iOS?
Tried with other password manager and it works correctly so this does not look like iOS bug.

@IhanaOlli commented on GitHub (Jul 17, 2020): Same issue here. iOS 13.6, iPhone 11 Pro Max, BW 2.5.0 (193). I uninstalled & reinstalled BW and autofill still remembers incorrect data from earlier, before reinstallation! I normally use Firefox on iOS and autofill using that shows old data. However, if I access same site with Safari and tap the 🔑 button on autofill bar and then "Bitwarden..." autofill data gets updated! So there is some kind of caching, maybe by iOS? Tried with other password manager and it works correctly so this does not look like iOS bug.
GiteaMirror commented 2025-11-26 22:37:40 -06:00
Author
Owner
Copy Link

@NPadrutt commented on GitHub (Jul 20, 2020):

@MattTheDev just to give you an update: I just had the same issue with a new entry for twitch. I created the entry on my laptop, closed the twitch on my iPad, synced in bitwarden, switched back to the twitch app and tried to autofill but couldn't find the entry although it was already available in the app.

@NPadrutt commented on GitHub (Jul 20, 2020): @MattTheDev just to give you an update: I just had the same issue with a new entry for twitch. I created the entry on my laptop, closed the twitch on my iPad, synced in bitwarden, switched back to the twitch app and tried to autofill but couldn't find the entry although it was already available in the app.
GiteaMirror commented 2025-11-26 22:37:41 -06:00
Author
Owner
Copy Link

@charles-curran commented on GitHub (Jul 20, 2020):

I also ran into this issue and I may have found the problem.

Like everyone else I've been running into the issue of the auto-fill function of Bitwarden not working on both my iPhone (11 Pro Max @ iOS 13.6 (17G68)) and my iPad (6th Generation @ iOS 13.6 (17G68)).

As suggested here I tried to save a new entry directly into the Bitwarden app and was not able to get it to auto-fill in Firefox (Version 27.0 (18428)), the newly added entry would not populate and searching for it did not work either. I tried closing out both Bitwarden and Firefox and trying again, that did not work. However restarting my phone did work.

With that I did a test. I replicated the issue above by adding a new entry and confirming that it was showing the cached data. I then went to Settings -> Safari -> Clear History and Website Data and this cleared the cache!

I've now tested this on a half dozen different entries to confirm, but clearing the Safari cache works every time, at least for me, that auto-fill starts showing cached data.

Hopefully this helps! I absolutely love this tool and appreciate all the work that goes into making it as great as it is!

@charles-curran commented on GitHub (Jul 20, 2020): I also ran into this issue and I may have found the problem. Like everyone else I've been running into the issue of the auto-fill function of Bitwarden not working on both my iPhone (11 Pro Max @ iOS 13.6 (17G68)) and my iPad (6th Generation @ iOS 13.6 (17G68)). As suggested here I tried to save a new entry directly into the Bitwarden app and was not able to get it to auto-fill in Firefox (Version 27.0 (18428)), the newly added entry would not populate and searching for it did not work either. I tried closing out both Bitwarden and Firefox and trying again, that did not work. However restarting my phone did work. With that I did a test. I replicated the issue above by adding a new entry and confirming that it was showing the cached data. I then went to Settings -> Safari -> Clear History and Website Data and this cleared the cache! I've now tested this on a half dozen different entries to confirm, but clearing the Safari cache works every time, at least for me, that auto-fill starts showing cached data. Hopefully this helps! I absolutely love this tool and appreciate all the work that goes into making it as great as it is!
GiteaMirror commented 2025-11-26 22:37:41 -06:00
Author
Owner
Copy Link

@NPadrutt commented on GitHub (Jul 21, 2020):

I can confirm that the work around of @charles-curran worked for me as well.

@NPadrutt commented on GitHub (Jul 21, 2020): I can confirm that the work around of @charles-curran worked for me as well.
GiteaMirror commented 2025-11-26 22:37:41 -06:00
Author
Owner
Copy Link

@trevorbayless commented on GitHub (Jul 23, 2020):

I'm having this same issue. Haven't seen anyone mention Android, but I'm running Android 10 on an S10e.

Add an entry via another source and autofill on the app won't have the login information. I have to open the app, sync, and then go back to the login prompt where the auto fill option will be updated.

@trevorbayless commented on GitHub (Jul 23, 2020): I'm having this same issue. Haven't seen anyone mention Android, but I'm running Android 10 on an S10e. Add an entry via another source and autofill on the app won't have the login information. I have to open the app, sync, and then go back to the login prompt where the auto fill option will be updated.
GiteaMirror commented 2025-11-26 22:37:42 -06:00
Author
Owner
Copy Link

@stub68 commented on GitHub (Jul 23, 2020):

In the end I deleted the accounts and started again with an externally generated strong password which I then copied to the iOS autofill. Not ideal obviously, but ok for me because the accounts were new and empty anyway.

@stub68 commented on GitHub (Jul 23, 2020): In the end I deleted the accounts and started again with an externally generated strong password which I then copied to the iOS autofill. Not ideal obviously, but ok for me because the accounts were new and empty anyway.
GiteaMirror commented 2025-11-26 22:37:42 -06:00
Author
Owner
Copy Link

@104manage commented on GitHub (Aug 17, 2020):

I read another user emptied the trash and this solved the issue. I tested the approach and after syncing my ios device found the PW stack no longer contained the prior passwords.

Reference:

https://community.bitwarden.com/t/still-using-old-password-on-ios-safari/13226/8

@104manage commented on GitHub (Aug 17, 2020): I read another user emptied the trash and this solved the issue. I tested the approach and after syncing my ios device found the PW stack no longer contained the prior passwords. Reference: https://community.bitwarden.com/t/still-using-old-password-on-ios-safari/13226/8
GiteaMirror commented 2025-11-26 22:37:42 -06:00
Author
Owner
Copy Link

@nokoa77 commented on GitHub (Aug 23, 2020):

I read another user emptied the trash and this solved the issue. I tested the approach and after syncing my ios device found the PW stack no longer contained the prior passwords.

Reference:

https://community.bitwarden.com/t/still-using-old-password-on-ios-safari/13226/8

Sorry I think this is another issue, the problem described here appears also when the trash is empty

@nokoa77 commented on GitHub (Aug 23, 2020): > I read another user emptied the trash and this solved the issue. I tested the approach and after syncing my ios device found the PW stack no longer contained the prior passwords. > > Reference: > > https://community.bitwarden.com/t/still-using-old-password-on-ios-safari/13226/8 Sorry I think this is another issue, the problem described here appears also when the trash is empty
GiteaMirror commented 2025-11-26 22:37:42 -06:00
Author
Owner
Copy Link

@jebeaudet commented on GitHub (Sep 6, 2020):

Any updates on this one @MattTheDev? Could you add a force refresh or something in the meantime? Thanks

@jebeaudet commented on GitHub (Sep 6, 2020): Any updates on this one @MattTheDev? Could you add a force refresh or something in the meantime? Thanks
GiteaMirror commented 2025-11-26 22:37:43 -06:00
Author
Owner
Copy Link

@jebeaudet commented on GitHub (Sep 6, 2020):

The affected iPhone was in french and since changing it to english, I no longer get the problem. Could localization be an issue here?

Are people on iOS affected here in a different language as well?

@jebeaudet commented on GitHub (Sep 6, 2020): The affected iPhone was in french and since changing it to english, I no longer get the problem. Could localization be an issue here? Are people on iOS affected here in a different language as well?
GiteaMirror commented 2025-11-26 22:37:43 -06:00
Author
Owner
Copy Link

@ma-neu commented on GitHub (Sep 6, 2020):

My affected iPhone is in german.

@ma-neu commented on GitHub (Sep 6, 2020): My affected iPhone is in german.
GiteaMirror commented 2025-11-26 22:37:43 -06:00
Author
Owner
Copy Link

@jebeaudet commented on GitHub (Sep 6, 2020):

Try switching temporaly to English to see if it resolves the issue you have!

@jebeaudet commented on GitHub (Sep 6, 2020): Try switching temporaly to English to see if it resolves the issue you have!
GiteaMirror commented 2025-11-26 22:37:43 -06:00
Author
Owner
Copy Link

@nokoa77 commented on GitHub (Sep 7, 2020):

Strange, I have the problem also, and my iPhone is on French

@nokoa77 commented on GitHub (Sep 7, 2020): Strange, I have the problem also, and my iPhone is on French
GiteaMirror commented 2025-11-26 22:37:44 -06:00
Author
Owner
Copy Link

@ewjoachim commented on GitHub (Sep 13, 2020):

I can’t be sure but what I understand (I’m affected by this bug too) is that there’s the bitwarden process launched by the app, and iOS maintains a separate process for the autofill features. When we change anything in the first process, the second process is not aware. The only workarounds (except not using the Autofill at all) would be whatever method that forces iOS to restart the bw autofill process (I believe it sync on startup), so changing the language (which restarts every app) is a solution, so is restarting the phone or uninstalling the app.
If there’s no simple way to control when iOS restarts the autofill process, I guess the only thing bw can do is refresh more often, or refresh on autofill.

@ewjoachim commented on GitHub (Sep 13, 2020): I can’t be sure but what I understand (I’m affected by this bug too) is that there’s the bitwarden process launched by the app, and iOS maintains a separate process for the autofill features. When we change anything in the first process, the second process is not aware. The only workarounds (except not using the Autofill at all) would be whatever method that forces iOS to restart the bw autofill process (I believe it sync on startup), so changing the language (which restarts every app) is a solution, so is restarting the phone or uninstalling the app. If there’s no simple way to control when iOS restarts the autofill process, I guess the only thing bw can do is refresh more often, or refresh on autofill.
GiteaMirror commented 2025-11-26 22:37:44 -06:00
Author
Owner
Copy Link

@jebeaudet commented on GitHub (Sep 13, 2020):

For me, it's not a matter of restarting apps/phone, since switching to english I don't have the problem anymore. The 2 commenters below me also have an iPhone with a different than english language though sadly they didn't try to change it it seems, so I'd be interested to see others trying it out.

@jebeaudet commented on GitHub (Sep 13, 2020): For me, it's not a matter of restarting apps/phone, since switching to english I don't have the problem anymore. The 2 commenters below me also have an iPhone with a different than english language though sadly they didn't try to change it it seems, so I'd be interested to see others trying it out.
GiteaMirror commented 2025-11-26 22:37:44 -06:00
Author
Owner
Copy Link

@prestr commented on GitHub (Sep 13, 2020):

I also have this issue on my iPhone's (iOS 13 and iOS 14 Beta 8). Going into Settings.app > Safari > Clear History and Website Data resolves it for me.

Note: This seems to affect auto-filling into all apps, not just Safari.

@prestr commented on GitHub (Sep 13, 2020): I also have this issue on my iPhone's (iOS 13 and iOS 14 Beta 8). Going into Settings.app > Safari > Clear History and Website Data resolves it for me. Note: This seems to affect auto-filling into all apps, not just Safari.
GiteaMirror commented 2025-11-26 22:37:45 -06:00
Author
Owner
Copy Link

@Tataru-Taru commented on GitHub (Oct 7, 2020):

I also have this issue on my iPhone's (iOS 13 and iOS 14 Beta 8). Going into Settings.app > Safari > Clear History and Website Data resolves it for me.

Note: This seems to affect auto-filling into all apps, not just Safari.

I can confirm this worked for me. Does this mean that Safari is actually caching the data and that's being fed to the autofill?

Doesn't that also mean that the data is exposed outside of Bitwarden and stored in Safari Data Cache?

@Tataru-Taru commented on GitHub (Oct 7, 2020): > I also have this issue on my iPhone's (iOS 13 and iOS 14 Beta 8). Going into Settings.app > Safari > Clear History and Website Data resolves it for me. > > Note: This seems to affect auto-filling into all apps, not just Safari. I can confirm this worked for me. Does this mean that Safari is actually caching the data and that's being fed to the autofill? Doesn't that also mean that the data is exposed outside of Bitwarden and stored in Safari Data Cache?
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
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#1045
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?