github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-05-07 03:23:29 -05:00
Code Issues 1.1k Packages Projects Releases 122 Wiki Activity

[GH-ISSUE #4308] Addy.io and SimpleLogin missing server URL option #27954

New Issue
Closed
opened 2026-04-18 11:40:41 -05:00 by GiteaMirror · 10 comments
GiteaMirror commented 2026-04-18 11:40:41 -05:00
Owner
Copy Link

Originally created by @PseudoResonance on GitHub (Nov 15, 2024).
Original GitHub issue: https://github.com/bitwarden/android/issues/4308

Steps To Reproduce

  1. Go to Generator
  2. Go to Username tab
  3. Choose Forwarded email alias type
  4. Choose addy.io or SimpleLogin service

Expected Result

Server URL should be configurable for self-hosted instances.

Actual Result

Server URL option is missing and the primary services are hard coded.

Screenshots or Videos

No response

Additional Context

While this is available on desktop, the option to configure custom URLs is just missing in the mobile app code for some reason, as seen here.
Also related to bitwarden/mobile/issues/3152 for the old app.

Build Version

2024.11.5 (19461)

What server are you connecting to?

Self-host

Self-host Server Version

Vaultwarden 2024.6.2

Environment Details

N/A

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 (Nov 15, 2024). Original GitHub issue: https://github.com/bitwarden/android/issues/4308 ### Steps To Reproduce 1. Go to Generator 2. Go to Username tab 3. Choose Forwarded email alias type 4. Choose addy.io or SimpleLogin service ### Expected Result Server URL should be configurable for self-hosted instances. ### Actual Result Server URL option is missing and the primary services are hard coded. ### Screenshots or Videos _No response_ ### Additional Context While this is available on desktop, the option to configure custom URLs is just missing in the mobile app code for some reason, [as seen here](https://github.com/bitwarden/android/blob/main/app/src/main/java/com/x8bit/bitwarden/ui/tools/feature/generator/util/ServiceTypeExtensions.kt). Also related to bitwarden/mobile/issues/3152 for the old app. ### Build Version 2024.11.5 (19461) ### What server are you connecting to? Self-host ### Self-host Server Version Vaultwarden 2024.6.2 ### Environment Details N/A ### 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 2026-04-18 11:40:41 -05:00
GiteaMirror commented 2026-04-18 11:40:43 -05:00
Author
Owner
Copy Link

@bitwarden-bot commented on GitHub (Nov 15, 2024):

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

<!-- gh-comment-id:2478273253 --> @bitwarden-bot commented on GitHub (Nov 15, 2024): Thank you for your report! We've added this to our internal board for review. ID: PM-14936
GiteaMirror commented 2026-04-18 11:40:45 -05:00
Author
Owner
Copy Link

@daniellbw commented on GitHub (Nov 18, 2024):

Hi there,

Thank you for your report!

I was able to reproduce this issue, and I have flagged this to our engineering team.

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!

<!-- gh-comment-id:2482213982 --> @daniellbw commented on GitHub (Nov 18, 2024): Hi there, Thank you for your report! I was able to reproduce this issue, and I have flagged this to our engineering team. 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!
GiteaMirror commented 2026-04-18 11:40:45 -05:00
Author
Owner
Copy Link

@BJReplay commented on GitHub (Dec 21, 2024):

Simple Login still missing URL in 2024.12.0 (19597)

<!-- gh-comment-id:2558018386 --> @BJReplay commented on GitHub (Dec 21, 2024): Simple Login still missing URL in 2024.12.0 (19597)
GiteaMirror commented 2026-04-18 11:40:46 -05:00
Author
Owner
Copy Link

@lunyx commented on GitHub (Apr 24, 2025):

Not sure why this is closed. Simplelogin still doesn't have the option and the linked PR only mentions anonaddy

<!-- gh-comment-id:2826122132 --> @lunyx commented on GitHub (Apr 24, 2025): Not sure why this is closed. Simplelogin still doesn't have the option and the linked PR only mentions anonaddy
GiteaMirror commented 2026-04-18 11:40:46 -05:00
Author
Owner
Copy Link

@PseudoResonance commented on GitHub (Apr 25, 2025):

Not sure why this is closed. Simplelogin still doesn't have the option and the linked PR only mentions anonaddy

The update is already available. Android clients have had both Addy.io and SimpleLogin since 2025.3.0 (19983). If you are on this version or newer already, the issue is probably because they are still locked behind feature flags at the moment.

I'm not entirely sure how feature flags work for the standard, Bitwarden managed cloud instance, however if you happen to be self hosting, including with Vaultwarden, you can define the feature flags through other means.

In the case of Vaultwarden, see this PR that adds them to the "valid flags" list. You can set the environment variable EXPERIMENTAL_CLIENT_FEATURE_FLAGS to include simple-login-self-host-alias or anon-addy-self-host-alias. Multiple flags can be specified by separating them with commas.

If you also use the Bitwarden iOS app though, these flags are still not available as of 2025.3.0. I'm not sure how Bitwarden's internal processes work, and if they will update this issue once it is fully resolved or not, but they are working on it.

<!-- gh-comment-id:2829610733 --> @PseudoResonance commented on GitHub (Apr 25, 2025): > Not sure why this is closed. Simplelogin still doesn't have the option and the linked PR only mentions anonaddy The update is already available. Android clients have had both Addy.io and SimpleLogin since [2025.3.0 (19983)](https://github.com/bitwarden/android/releases/tag/untagged-4731eaadac73f3dfbbb8). If you are on this version or newer already, the issue is probably because they are still [locked behind feature flags](https://contributing.bitwarden.com/contributing/feature-flags/) at the moment. I'm not entirely sure how feature flags work for the standard, Bitwarden managed cloud instance, however if you happen to be self hosting, including with Vaultwarden, you can define the feature flags through other means. In the case of Vaultwarden, [see this PR](https://github.com/dani-garcia/vaultwarden/pull/5694) that adds them to the "valid flags" list. You can set the environment variable `EXPERIMENTAL_CLIENT_FEATURE_FLAGS` to include `simple-login-self-host-alias` or `anon-addy-self-host-alias`. Multiple flags can be specified by separating them with commas. If you also use the Bitwarden iOS app though, [these flags are still not available](https://github.com/bitwarden/ios/issues/1436#issuecomment-2730495741) as of 2025.3.0. I'm not sure how Bitwarden's internal processes work, and if they will update this issue once it is fully resolved or not, but they are working on it.
GiteaMirror commented 2026-04-18 11:40:48 -05:00
Author
Owner
Copy Link

@lunyx commented on GitHub (Apr 25, 2025):

Thanks for the clarification. I guess the bitwarden PR is separate and wasn't linked. Yes, that is the version I'm on currently, so I'll just wait to see when they get enabled.

<!-- gh-comment-id:2830372337 --> @lunyx commented on GitHub (Apr 25, 2025): Thanks for the clarification. I guess the bitwarden PR is separate and wasn't linked. Yes, that is the version I'm on currently, so I'll just wait to see when they get enabled.
GiteaMirror commented 2026-04-18 11:40:49 -05:00
Author
Owner
Copy Link

@PseudoResonance commented on GitHub (Apr 26, 2025):

Thanks for the clarification. I guess the bitwarden PR is separate and wasn't linked. Yes, that is the version I'm on currently, so I'll just wait to see when they get enabled.

From my understanding, Bitwarden is probably waiting for the iOS update to be finished and make sure it's working well before they permanently activate the feature flags. It'll presumably be a while, but who knows. I'm not affiliated with Bitwarden in any way, I just documented this issue.

<!-- gh-comment-id:2831777679 --> @PseudoResonance commented on GitHub (Apr 26, 2025): > Thanks for the clarification. I guess the bitwarden PR is separate and wasn't linked. Yes, that is the version I'm on currently, so I'll just wait to see when they get enabled. From my understanding, Bitwarden is probably waiting for the iOS update to be finished and make sure it's working well before they permanently activate the feature flags. It'll presumably be a while, but who knows. I'm not affiliated with Bitwarden in any way, I just documented this issue.
GiteaMirror commented 2026-04-18 11:40:50 -05:00
Author
Owner
Copy Link

@SaintPatrck commented on GitHub (Apr 28, 2025):

Hi all,

These feature flags are schedule to be enabled in the next release, 2025.4.0.

<!-- gh-comment-id:2835414397 --> @SaintPatrck commented on GitHub (Apr 28, 2025): Hi all, These feature flags are schedule to be enabled in the next release, `2025.4.0`.
GiteaMirror commented 2026-04-18 11:40:51 -05:00
Author
Owner
Copy Link

@PseudoResonance commented on GitHub (Apr 30, 2025):

Hi all,

These feature flags are schedule to be enabled in the next release, 2025.4.0.

Do you know anything about the state of the iOS implementation? No worries if you don't/can't though. Was just wondering if the 2025.4.0 is scheduled to line up with iOS release of it, or if iOS is going to have its own, unique flags in the future or something.

<!-- gh-comment-id:2840866691 --> @PseudoResonance commented on GitHub (Apr 30, 2025): > Hi all, > > These feature flags are schedule to be enabled in the next release, `2025.4.0`. Do you know anything about the state of the iOS implementation? No worries if you don't/can't though. Was just wondering if the 2025.4.0 is scheduled to line up with iOS release of it, or if iOS is going to have its own, unique flags in the future or something.
GiteaMirror commented 2026-04-18 11:40:51 -05:00
Author
Owner
Copy Link

@SaintPatrck commented on GitHub (Apr 30, 2025):

Hey @@PseudoResonance

iOS flags will also be enabled in the next release.

<!-- gh-comment-id:2842012643 --> @SaintPatrck commented on GitHub (Apr 30, 2025): Hey @@PseudoResonance iOS flags will also be enabled in the next release.
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#27954
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?