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

[PM-25999] Saving Signal Backups key to password manager does not work #2355

New Issue
Open
opened 2025-11-26 23:16:34 -06:00 by GiteaMirror · 3 comments
GiteaMirror commented 2025-11-26 23:16:34 -06:00
Owner
Copy Link

Originally created by @lucasmz-dev on GitHub (Sep 19, 2025).

Steps To Reproduce

  1. Test them new Signal Backups
  2. When creating the backup and the key is generated, click "Save to password manager"

Expected Result

Bitwarden allows saving the key to the vault.

Actual Result

Nothing happens

Screenshots or Videos

No response

Additional Context

On googled devices, so most of them, this instead redirects to the Google Password Manager which is risky

Build Version

2025.8.1

What server are you connecting to?

US

Self-host Server Version

No response

Environment Details

  • Device: moto g52
  • OS: iodéOS (which is LineageOS 22.2, which is Android 15 QPR2 for all intents and purposes)

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 @lucasmz-dev on GitHub (Sep 19, 2025). ### Steps To Reproduce 1. Test them new Signal Backups 2. When creating the backup and the key is generated, click "Save to password manager" ### Expected Result Bitwarden allows saving the key to the vault. ### Actual Result Nothing happens ### Screenshots or Videos _No response_ ### Additional Context On googled devices, so most of them, this instead redirects to the Google Password Manager which is risky ### Build Version 2025.8.1 ### What server are you connecting to? US ### Self-host Server Version _No response_ ### Environment Details - Device: moto g52 - OS: iodéOS (which is LineageOS 22.2, which is Android 15 QPR2 for all intents and purposes) ### 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 app:password-managerbug labels 2025-11-26 23:16:34 -06:00
GiteaMirror commented 2025-11-26 23:16:34 -06:00
Author
Owner
Copy Link

@bitwarden-bot commented on GitHub (Sep 19, 2025):

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

@bitwarden-bot commented on GitHub (Sep 19, 2025): Thank you for your report! We've added this to our internal board for review. ID: PM-25999
GiteaMirror commented 2025-11-26 23:16:34 -06:00
Author
Owner
Copy Link

@lucasmz-dev commented on GitHub (Sep 19, 2025):

https://community.signalusers.org/t/public-signal-backups-testing/69984/90?u=lucasmz

@lucasmz-dev commented on GitHub (Sep 19, 2025): https://community.signalusers.org/t/public-signal-backups-testing/69984/90?u=lucasmz
GiteaMirror commented 2025-11-26 23:16:35 -06:00
Author
Owner
Copy Link

@rmcdowell-bitwarden commented on GitHub (Sep 24, 2025):

Hi there,

Thank you for your report!

I was able to reproduce this issue, and received the following message:

Can't save to password manager

You don't have a password manger set up, or the password manager you're using isn't supported.

I have flagged this to our engineering team in case there is any action that needs to be taken on their end in conjuncture with Signal

If you wish to add any further information/screenshots/recordings etc., please feel free to do so at any time - our engineering team will be happy to review these.

Thanks once again!

@rmcdowell-bitwarden commented on GitHub (Sep 24, 2025): Hi there, Thank you for your report! I was able to reproduce this issue, and received the following message: Can't save to password manager You don't have a password manger set up, or the password manager you're using isn't supported. I have flagged this to our engineering team in case there is any action that needs to be taken on their end in conjuncture with Signal If you wish to add any further information/screenshots/recordings etc., please feel free to do so at any time - our engineering team will be happy to review these. Thanks once again!
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
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#2355
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?