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

[GH-ISSUE #6448] [PM-31469] Website URIs not preferred over the first URI (e.g. androidapp://) #50534

New Issue
Open
opened 2026-05-01 13:31:10 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-05-01 13:31:10 -05:00
Owner
Copy Link

Originally created by @lucasmz-dev on GitHub (Jan 30, 2026).
Original GitHub issue: https://github.com/bitwarden/android/issues/6448

Steps To Reproduce

  1. Have a login item that has the first URI as Android app://
  2. Also have an https:// URI set up
  3. The login item icon will be the Android icon
  4. Compare to other platforms

Expected Result

When an HTTP URI is available, it should use that as a priority

Actual Result

Website URI is not prioritized

Screenshots or Videos

No response

Additional Context

No response

Build Version

2026.1.0

What server are you connecting to?

US

Self-host Server Version

No response

Environment Details

All devices

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 (Jan 30, 2026). Original GitHub issue: https://github.com/bitwarden/android/issues/6448 ### Steps To Reproduce 1. Have a login item that has the first URI as Android app:// 2. Also have an https:// URI set up 3. The login item icon will be the Android icon 4. Compare to other platforms ### Expected Result When an HTTP URI is available, it should use that as a priority ### Actual Result Website URI is not prioritized ### Screenshots or Videos _No response_ ### Additional Context _No response_ ### Build Version 2026.1.0 ### What server are you connecting to? US ### Self-host Server Version _No response_ ### Environment Details All devices ### 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-05-01 13:31:10 -05:00
GiteaMirror commented 2026-05-01 13:31:17 -05:00
Author
Owner
Copy Link

@bitwarden-bot commented on GitHub (Jan 30, 2026):

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

<!-- gh-comment-id:3825050562 --> @bitwarden-bot commented on GitHub (Jan 30, 2026): Thank you for your report! We've added this to our internal board for review. ID: [PM-31469](https://bitwarden.atlassian.net/browse/PM-31469) [PM-31469]: https://bitwarden.atlassian.net/browse/PM-31469?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ
GiteaMirror commented 2026-05-01 13:31:20 -05:00
Author
Owner
Copy Link

@TroyBW commented on GitHub (Jan 31, 2026):

Hi there,

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 recreate 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!

<!-- gh-comment-id:3827141831 --> @TroyBW commented on GitHub (Jan 31, 2026): Hi there, 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 recreate 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 2026-05-01 13:31:26 -05:00
Author
Owner
Copy Link

@lucasmz-dev commented on GitHub (Jan 31, 2026):

I wouldn't consider this as a feature request considering Bitwarden on other platforms doesn't behave like this. The xamarin app also didn't IIRC. It seems to be some sort of special handling that was in Bitwarden clients that kind of disappeared on the new apps.

<!-- gh-comment-id:3829277813 --> @lucasmz-dev commented on GitHub (Jan 31, 2026): I wouldn't consider this as a feature request considering Bitwarden on other platforms doesn't behave like this. The xamarin app also didn't IIRC. It seems to be some sort of special handling that was in Bitwarden clients that kind of disappeared on the new apps.
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#50534
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?