github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-07-22 15:21:28 -05:00
Code Issues 2.4k Packages Projects Releases 129 Wiki Activity

[GH-ISSUE #7042] [PM-38764] Forwarded email aliases are generated immediately upon viewing the page, rather than after confirming #127810

New Issue
Open
opened 2026-06-13 21:14:49 -05:00 by GiteaMirror · 4 comments
GiteaMirror commented 2026-06-13 21:14:49 -05:00
Owner
Copy Link
Copy Source

Originally created by @PseudoResonance on GitHub (Jun 9, 2026).
Original GitHub issue: https://github.com/bitwarden/android/issues/7042

Steps To Reproduce

  1. Go to "Generator"
  2. Click "Username"

Expected Result

Alias should only be generated after clicking a button to confirm.

Actual Result

Alias will be immediately generated upon viewing the page, which can accidentally generate/save a bunch of unused aliases at the service every time you click generator. It makes it really hard to tell what aliases are real and which are garbage that Bitwarden generated when I didn't need it.

Screenshots or Videos

No response

Additional Context

The browser extension functions properly, and requires clicking the "generate" button to generate the initial alias, in order to prevent cluttering up the alias service. By default, the alias field simply says -.

I am specifically using Addy.io, but I suspect the behavior is the same on any service.

Build Version

2026.4.2

What server are you connecting to?

Self-host

Self-host Server Version

Vaultwarden 1.36.0

Environment Details

No response

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 @PseudoResonance on GitHub (Jun 9, 2026). Original GitHub issue: https://github.com/bitwarden/android/issues/7042 ### Steps To Reproduce 1. Go to "Generator" 2. Click "Username" ### Expected Result Alias should only be generated after clicking a button to confirm. ### Actual Result Alias will be immediately generated upon viewing the page, which can accidentally generate/save a bunch of unused aliases at the service every time you click generator. It makes it really hard to tell what aliases are real and which are garbage that Bitwarden generated when I didn't need it. ### Screenshots or Videos _No response_ ### Additional Context The browser extension functions properly, and requires clicking the "generate" button to generate the initial alias, in order to prevent cluttering up the alias service. By default, the alias field simply says `-`. I am specifically using Addy.io, but I suspect the behavior is the same on any service. ### Build Version 2026.4.2 ### What server are you connecting to? Self-host ### Self-host Server Version Vaultwarden 1.36.0 ### Environment Details _No response_ ### 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 bugapp:password-manager labels 2026-06-13 21:14:50 -05:00
GiteaMirror commented 2026-06-13 21:14:51 -05:00
Author
Owner
Copy Link
Copy Source

@bitwarden-bot commented on GitHub (Jun 9, 2026):

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

<!-- gh-comment-id:4659216969 --> @bitwarden-bot commented on GitHub (Jun 9, 2026): Thank you for your report! We've added this to our internal board for review. ID: [PM-38764](https://bitwarden.atlassian.net/browse/PM-38764) [PM-38764]: https://bitwarden.atlassian.net/browse/PM-38764?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ
GiteaMirror commented 2026-06-13 21:14:52 -05:00
Author
Owner
Copy Link
Copy Source

@PseudoResonance commented on GitHub (Jun 9, 2026):

The issue is also present on iOS, bitwarden/ios#1571

<!-- gh-comment-id:4659218304 --> @PseudoResonance commented on GitHub (Jun 9, 2026): The issue is also present on iOS, bitwarden/ios#1571
GiteaMirror commented 2026-06-13 21:14:52 -05:00
Author
Owner
Copy Link
Copy Source

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

Another user here.

And I would guess, this response by @Krychaz would still be valid: https://github.com/bitwarden/android/issues/6357#issuecomment-3755788146

<!-- gh-comment-id:4659450871 --> @pamperer562580892423 commented on GitHub (Jun 9, 2026): Another user here. And I would guess, this response by @Krychaz would still be valid: https://github.com/bitwarden/android/issues/6357#issuecomment-3755788146
GiteaMirror commented 2026-06-13 21:14:53 -05:00
Author
Owner
Copy Link
Copy Source

@PseudoResonance commented on GitHub (Jun 9, 2026):

That's about passwords though, which while annoying is less of a problem in my opinion. Aliases on an external service are going to be calling the API every single time and making a new alias that clutters everything up.

<!-- gh-comment-id:4659961712 --> @PseudoResonance commented on GitHub (Jun 9, 2026): That's about passwords though, which while annoying is less of a problem in my opinion. Aliases on an external service are going to be calling the API every single time and making a new alias that clutters everything up.
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 labels app:password-manager bug
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
GiteaMirror ninjasurge (Kaehlen Rog)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#127810