github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-03-22 20:41:29 -05:00
Code Issues 144 Packages Projects Releases 118 Wiki Activity

Autofill doesn't work in Vanadium (Chrome) #1544

New Issue
Closed
opened 2025-11-26 22:52:07 -06:00 by GiteaMirror · 4 comments
GiteaMirror commented 2025-11-26 22:52:07 -06:00
Owner
Copy Link

Originally created by @Morpheus0x on GitHub (Dec 14, 2022).

Steps To Reproduce

  1. Open Vanadium Browser (GrapheneOS Chrome fork)
  2. Go to any login page, e.g. github
  3. Clicking on either username or password field doesn't show the Autofill
  4. Clicking on the Auto-fill tile from quick settings (notifications drop-down) produces toast message "No password fields detected" and switches to bitwarden app

Expected Result

The bitwarden autofill option should pop up, allowing the user to choose what saved username and password should be filled in

Actual Result

Nothing shows up

Screenshots or Videos

No response

Additional Context

Vanadium 108.0
Bitwarden 2022.11.0 (was working in 2022.10.0)

Operating System

Android

Operating System Version

Android 13 (latest GrapheneOS)

Device

Pixel 6 & Pixel 5

Build Version

2022.11.0

Beta

  • Using a pre-release version of the application.
Originally created by @Morpheus0x on GitHub (Dec 14, 2022). ### Steps To Reproduce 1. Open Vanadium Browser (GrapheneOS Chrome fork) 2. Go to any login page, e.g. github 3. Clicking on either username or password field doesn't show the Autofill 4. Clicking on the Auto-fill tile from quick settings (notifications drop-down) produces toast message "No password fields detected" and switches to bitwarden app ### Expected Result The bitwarden autofill option should pop up, allowing the user to choose what saved username and password should be filled in ### Actual Result Nothing shows up ### Screenshots or Videos _No response_ ### Additional Context Vanadium 108.0 Bitwarden 2022.11.0 (was working in 2022.10.0) ### Operating System Android ### Operating System Version Android 13 (latest GrapheneOS) ### Device Pixel 6 & Pixel 5 ### Build Version 2022.11.0 ### Beta - [ ] Using a pre-release version of the application.
GiteaMirror added the bug label 2025-11-26 22:52:07 -06:00
GiteaMirror commented 2025-11-26 22:52:07 -06:00
Author
Owner
Copy Link

@djsmith85 commented on GitHub (Dec 14, 2022):

Hi @Morpheus0x, thank you for your report.

This has been fixed by a community contribution via https://github.com/bitwarden/mobile/pull/2199.

The changes will be included in an upcoming release.

@djsmith85 commented on GitHub (Dec 14, 2022): Hi @Morpheus0x, thank you for your report. This has been fixed by a community contribution via https://github.com/bitwarden/mobile/pull/2199. The changes will be included in an upcoming release.
GiteaMirror commented 2025-11-26 22:52:07 -06:00
Author
Owner
Copy Link

@Enlinks commented on GitHub (Jan 22, 2023):

I wanted to report that this still is not work after Bitwardens #2199

I've tested this on my normal phone running Vanadium in compatibility mode commit and also my test phone that I formatted to get the non--compatibility mode Vanadium.

version 109.0.5414.86
app.vanadium.browser
versionCode 541408633
targetSdk 33
minSdk 29
Installed: Jan 1, 2009; 12:00 AM

version 2023.1.0
com.x8bit.bitwarden
versionCode 5786
targetSdk 33
minSdk 21
Installed: Jan 22, 2023; 8:53 PM
@Enlinks commented on GitHub (Jan 22, 2023): I wanted to report that this still is not work after Bitwardens #2199 I've tested this on my normal phone running Vanadium in compatibility mode [commit](https://github.com/GrapheneOS/Vanadium/commit/fd37911a5e927298cefbb77e7460ef76219e7280) and also my test phone that I formatted to get the non--compatibility mode Vanadium. ``` version 109.0.5414.86 app.vanadium.browser versionCode 541408633 targetSdk 33 minSdk 29 Installed: Jan 1, 2009; 12:00 AM version 2023.1.0 com.x8bit.bitwarden versionCode 5786 targetSdk 33 minSdk 21 Installed: Jan 22, 2023; 8:53 PM
GiteaMirror commented 2025-11-26 22:52:08 -06:00
Author
Owner
Copy Link

@thestinger commented on GitHub (Jan 22, 2023):

Bitwarden needs to ship a release with the change if they haven't done that yet.

@thestinger commented on GitHub (Jan 22, 2023): Bitwarden needs to ship a release with the change if they haven't done that yet.
GiteaMirror commented 2025-11-26 22:52:08 -06:00
Author
Owner
Copy Link

@Enlinks commented on GitHub (Jan 22, 2023):

@thestinger I have the release they added it, its in my above output.

version 2023.1.0

com.x8bit.bitwarden
versionCode 5786

targetSdk 33
minSdk 21

Installed: Jan 22, 2023; 8:53 PM
@Enlinks commented on GitHub (Jan 22, 2023): @thestinger I have the release they added it, its in my above output. ``` version 2023.1.0 com.x8bit.bitwarden versionCode 5786 targetSdk 33 minSdk 21 Installed: Jan 22, 2023; 8:53 PM
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#1544
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?