github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-06-11 09:06:13 -05:00
Code Issues 2.2k Packages Projects Releases 127 Wiki Activity

Catch all email generator has no option for appending URI as prefix #1994

New Issue
Closed
opened 2025-11-26 23:03:58 -06:00 by GiteaMirror · 3 comments
GiteaMirror commented 2025-11-26 23:03:58 -06:00
Owner
Copy Link

Originally created by @Serrated3150 on GitHub (Aug 30, 2024).

Bitwarden Beta

  • I'm using the new native Bitwarden Beta app and I'm aware that legacy .NET app bugs should be reported in bitwarden/mobile

Steps To Reproduce

  1. Add new item into Bitwarden vault.
  2. Fill in the URI with any details.
  3. Click on the generate username button.
  4. Select Catch-all email from the drop down.
  5. Fill in the domain details.
  6. No additional options for using the URI to generate a username exists.

Expected Result

An additional dropdown to select randomly generated prefix for the catch all email address or a URI host based prefix should exist.

Actual Result

No dropdown exists for generating the prefix. The only option is to use a randomly generated prefix.

Screenshots or Videos

No response

Additional Context

No response

Build Version

© Bitwarden Inc. 2015-2024 Version: 2024.8.0 (18985)

Environment Details

Samsung Galaxy S22
Android 14
One UI 6.1
August Security Patch

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 @Serrated3150 on GitHub (Aug 30, 2024). ### Bitwarden Beta - [X] I'm using the new native Bitwarden Beta app and I'm aware that legacy .NET app bugs should be reported in [bitwarden/mobile](https://github.com/bitwarden/mobile) ### Steps To Reproduce 1. Add new item into Bitwarden vault. 2. Fill in the URI with any details. 3. Click on the generate username button. 4. Select Catch-all email from the drop down. 5. Fill in the domain details. 6. No additional options for using the URI to generate a username exists. ### Expected Result An additional dropdown to select randomly generated prefix for the catch all email address or a URI host based prefix should exist. ### Actual Result No dropdown exists for generating the prefix. The only option is to use a randomly generated prefix. ### Screenshots or Videos _No response_ ### Additional Context _No response_ ### Build Version © Bitwarden Inc. 2015-2024 Version: 2024.8.0 (18985) ### Environment Details Samsung Galaxy S22 Android 14 One UI 6.1 August Security Patch ### 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 label 2025-11-26 23:03:58 -06:00
GiteaMirror commented 2025-11-26 23:03:59 -06:00
Author
Owner
Copy Link

@bitwarden-bot commented on GitHub (Aug 30, 2024):

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

@bitwarden-bot commented on GitHub (Aug 30, 2024): Thank you for your report! We've added this to our internal board for review. ID: PM-11501
GiteaMirror commented 2025-11-26 23:03:59 -06:00
Author
Owner
Copy Link

@Adedamola-Aina commented on GitHub (Sep 2, 2024):

Hi @Serrated3150

We use GitHub issues as a place to track bugs and other development related issues. The Bitwarden Community Forums has a Feature Requests section for submitting, voting for, and discussing requests like this one: https://community.bitwarden.com/c/feature-requests/

Please sign up on our forums and search to see if this request already exists (https://community.bitwarden.com/signup). If so, you can vote for it and contribute to any discussions about it. If not, you can re-create the request there so that it can be properly tracked.

This issue will now be closed. Note that the “Closed as not planned” status is for internal tracking purposes only, please do not hesitate to send us your suggestions to the forum.

Thanks!

@Adedamola-Aina commented on GitHub (Sep 2, 2024): Hi @Serrated3150 We use GitHub issues as a place to track bugs and other development related issues. The Bitwarden Community Forums has a Feature Requests section for submitting, voting for, and discussing requests like this one: https://community.bitwarden.com/c/feature-requests/ Please sign up on our forums and search to see if this request already exists (https://community.bitwarden.com/signup). If so, you can vote for it and contribute to any discussions about it. If not, you can re-create the request there so that it can be properly tracked. This issue will now be closed. Note that the “Closed as not planned” status is for internal tracking purposes only, please do not hesitate to send us your suggestions to the forum. Thanks!
GiteaMirror commented 2025-11-26 23:04:00 -06:00
Author
Owner
Copy Link

@Serrated3150 commented on GitHub (Sep 2, 2024):

Hi @Adedamola-Aina,

I disagree that this is a feature request as this functionality is on the main release of the Bitwarden Android app but is not in the beta release of the new Bitwarden Android app. Happy to be corrected but I believe features that are missing in the beta but are available in the main release should count as bugs.

@Serrated3150 commented on GitHub (Sep 2, 2024): Hi @Adedamola-Aina, I disagree that this is a feature request as this functionality is on the main release of the Bitwarden Android app but is not in the beta release of the new Bitwarden Android app. Happy to be corrected but I believe features that are missing in the beta but are available in the main release should count as bugs.
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#1994
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?