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

[PR #2199] [MERGED] [PS-1896] Add support for Vanadium in GrapheneOS #33923

New Issue
Closed
opened 2026-04-21 01:36:29 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-21 01:36:29 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/bitwarden/android/pull/2199
Author: @flawedworld
Created: 11/18/2022
Status: ✅ Merged
Merged: 12/8/2022
Merged by: @mpbw2

Base: master ← Head: vanadium-rebrand

📝 Commits (2)

  • 6fc88a7 Add support for Vanadium in GrapheneOS
  • 760c662 Merge branch 'master' into vanadium-rebrand

📊 Changes

3 files changed (+5 additions, -0 deletions)

View changed files

📝 src/Android/Accessibility/AccessibilityHelpers.cs (+1 -0)
📝 src/Android/Autofill/AutofillHelpers.cs (+1 -0)
📝 src/Android/Resources/xml/autofillservice.xml (+3 -0)

📄 Description

Type of change

  • Bug fix
  • New feature development
  • Tech debt (refactoring, code cleanup, dependency upgrades, etc)
  • Build/deploy pipeline (DevOps)
  • Other

Objective

GrapheneOS changed the package name of Vanadium from org.chromium.chrome to app.vanadium.browser so a new entry is needed for Bitwarden to work with Vanadium. See: fd37911a5e

Code changes

I just added app.vanadium.browser as a supported Chromium browser.

Screenshots

Before you submit

  • Please check for formatting errors (dotnet format --verify-no-changes) (required)
  • Please add unit tests where it makes sense to do so (encouraged but not required)
  • If this change requires a documentation update - notify the documentation team
  • If this change has particular deployment requirements - notify the DevOps team

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/bitwarden/android/pull/2199 **Author:** [@flawedworld](https://github.com/flawedworld) **Created:** 11/18/2022 **Status:** ✅ Merged **Merged:** 12/8/2022 **Merged by:** [@mpbw2](https://github.com/mpbw2) **Base:** `master` ← **Head:** `vanadium-rebrand` --- ### 📝 Commits (2) - [`6fc88a7`](https://github.com/bitwarden/android/commit/6fc88a7226e4edf1b7b5027c2de151424e89cd0d) Add support for Vanadium in GrapheneOS - [`760c662`](https://github.com/bitwarden/android/commit/760c66281e39a5a6e6775f8ac417696e7431b67e) Merge branch 'master' into vanadium-rebrand ### 📊 Changes **3 files changed** (+5 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `src/Android/Accessibility/AccessibilityHelpers.cs` (+1 -0) 📝 `src/Android/Autofill/AutofillHelpers.cs` (+1 -0) 📝 `src/Android/Resources/xml/autofillservice.xml` (+3 -0) </details> ### 📄 Description ## Type of change - [x] Bug fix - [ ] New feature development - [ ] Tech debt (refactoring, code cleanup, dependency upgrades, etc) - [ ] Build/deploy pipeline (DevOps) - [ ] Other ## Objective <!--Describe what the purpose of this PR is. For example: what bug you're fixing or what new feature you're adding--> GrapheneOS changed the package name of Vanadium from org.chromium.chrome to app.vanadium.browser so a new entry is needed for Bitwarden to work with Vanadium. See: https://github.com/GrapheneOS/Vanadium/commit/fd37911a5e927298cefbb77e7460ef76219e7280 ## Code changes <!--Explain the changes you've made to each file or major component. This should help the reviewer understand your changes--> <!--Also refer to any related changes or PRs in other repositories--> I just added app.vanadium.browser as a supported Chromium browser. ## Screenshots <!--Required for any UI changes. Delete if not applicable--> ## Before you submit - Please check for formatting errors (`dotnet format --verify-no-changes`) (required) - Please add **unit tests** where it makes sense to do so (encouraged but not required) - If this change requires a **documentation update** - notify the documentation team - If this change has particular **deployment requirements** - notify the DevOps team --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-04-21 01:36:29 -05:00
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 pull-request
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#33923
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?