github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-06-20 12:38:11 -05:00
Code Issues 2.4k Packages Projects Releases 129 Wiki Activity

Autofill issue with Firefox 83.1 (Android 9/10) #1147

New Issue
Closed
opened 2025-11-26 22:40:27 -06:00 by GiteaMirror · 5 comments
GiteaMirror commented 2025-11-26 22:40:27 -06:00
Owner
Copy Link

Originally created by @daviddem1971 on GitHub (Dec 7, 2020).

Describe the Bug

It seems enabling accessibility in BW interferes with autofill in Firefox.

Steps To Reproduce

  1. in BW autofill services, enable autofill, disable accessibility
  2. open Google sign-in in Firefox (or any other site with matching logins in your vault)
  3. as expected, obtain a BW pop up with possible matches from the vault
  4. in BW autofill, enable autofill, enable accessibility, enable draw over
  5. open Google sign-in in Firefox
  6. now the possible matches from the vault do not show up. Only the "go to my vault" option:

Expected Result

Expected that Firefox would favor autofill over accessibility, as do other browsers and apps

Actual Result

Autofill does not work in Firefox when accessibility is enabled in BW

Screenshots or Videos

Firefox with autofill enabled and accessibility disabled in BW:

Screenshot 1

Firefox with autofill, accessibility and draw over enabled in BW:

Screenshot 2

Environment

  • Device: Samsung S9+ / Samsung A20e
  • Operating system: Android 9 / Android 10
  • Firefox 83.1 or Firefox 84 beta
  • BW app 2.7.0 (3258)

Additional Context

I did try the above with the BW extension for Firefox enabled or disabled, still same result.

Originally created by @daviddem1971 on GitHub (Dec 7, 2020). <!-- Comment: Please do not submit feature requests. The [Community Forums][1] has a section for submitting, voting for, and discussing product feature requests. [1]: https://community.bitwarden.com --> ## Describe the Bug <!-- Comment: A clear and concise description of what the bug is. --> It seems enabling accessibility in BW interferes with autofill in Firefox. ## Steps To Reproduce <!-- Comment: How can we reproduce the behavior: --> 1. in BW autofill services, enable autofill, disable accessibility 2. open Google sign-in in Firefox (or any other site with matching logins in your vault) 3. as expected, obtain a BW pop up with possible matches from the vault 4. in BW autofill, enable autofill, enable accessibility, enable draw over 5. open Google sign-in in Firefox 6. now the possible matches from the vault do not show up. Only the "go to my vault" option: ## Expected Result <!-- Comment: A clear and concise description of what you expected to happen. --> Expected that Firefox would favor autofill over accessibility, as do other browsers and apps ## Actual Result <!-- Comment: A clear and concise description of what is happening. --> Autofill does not work in Firefox when accessibility is enabled in BW ## Screenshots or Videos <!-- Comment: If applicable, add screenshots and/or a short video to help explain your problem. --> Firefox with autofill enabled and accessibility disabled in BW: ![Screenshot 1](https://user-images.githubusercontent.com/47311661/101362327-421c3600-38a0-11eb-8c49-0994b0dc26d8.png) Firefox with autofill, accessibility and draw over enabled in BW: ![Screenshot 2](https://user-images.githubusercontent.com/47311661/101362463-6c6df380-38a0-11eb-8e12-81fb871ac11e.png) ## Environment - Device: Samsung S9+ / Samsung A20e - Operating system: Android 9 / Android 10 - Firefox 83.1 or Firefox 84 beta - BW app 2.7.0 (3258) ## Additional Context <!-- Comment: Add any other context about the problem here. --> I did try the above with the BW extension for Firefox enabled or disabled, still same result.
GiteaMirror commented 2025-11-26 22:40:28 -06:00
Author
Owner
Copy Link

@SergeantConfused commented on GitHub (Dec 7, 2020):

Hi there,

Thank you for bringing this to our attention.
Do you happen to have a Samsung device and have Bitwarden installed in the Secure Folder too?

Thank you in advance,

@SergeantConfused commented on GitHub (Dec 7, 2020): Hi there, Thank you for bringing this to our attention. Do you happen to have a Samsung device and have Bitwarden installed in the Secure Folder too? Thank you in advance,
GiteaMirror commented 2025-11-26 22:40:28 -06:00
Author
Owner
Copy Link

@daviddem1971 commented on GitHub (Dec 7, 2020):

Hi there,

Thank you for bringing this to our attention.
Do you happen to have a Samsung device and have Bitwarden installed in the Secure Folder too?

Thank you in advance,

It is a rooted Samsung S9+ with a custom ROM without secure folder. Normal BW installation from Playstore.

I do have another non-rooted Samsung device with Android 10 if you need me to do some testing.

@daviddem1971 commented on GitHub (Dec 7, 2020): > > > Hi there, > > Thank you for bringing this to our attention. > Do you happen to have a Samsung device and have Bitwarden installed in the Secure Folder too? > > Thank you in advance, It is a rooted Samsung S9+ with a custom ROM without secure folder. Normal BW installation from Playstore. I do have another non-rooted Samsung device with Android 10 if you need me to do some testing.
GiteaMirror commented 2025-11-26 22:40:28 -06:00
Author
Owner
Copy Link

@daviddem1971 commented on GitHub (Dec 7, 2020):

Tested with my non-rooted Samsung A20e (Android 10), basically new out of the box + latest OTA updates. Fresh installed Firefox and Bitwarden app: same issue.

@daviddem1971 commented on GitHub (Dec 7, 2020): Tested with my non-rooted Samsung A20e (Android 10), basically new out of the box + latest OTA updates. Fresh installed Firefox and Bitwarden app: same issue.
GiteaMirror commented 2025-11-26 22:40:28 -06:00
Author
Owner
Copy Link

@LaXiS96 commented on GitHub (Jan 26, 2021):

Same issue here, but I may have "fixed" it. On a OnePlus 6 running both Firefox 84.1.4 and Firefox Nightly 210124 17:01.

Had both app and Firefox extension installed, with autofill service enabled, accessibility disabled. Removing the Firefox extension made no difference. What helped was simply disabling and reenabling the autofill service, after that I haven't seen the second popup again.

@LaXiS96 commented on GitHub (Jan 26, 2021): Same issue here, but I may have "fixed" it. On a OnePlus 6 running both Firefox 84.1.4 and Firefox Nightly 210124 17:01. Had both app and Firefox extension installed, with autofill service enabled, accessibility disabled. Removing the Firefox extension made no difference. What helped was simply disabling and reenabling the autofill service, after that I haven't seen the second popup again.
GiteaMirror commented 2025-11-26 22:40:29 -06:00
Author
Owner
Copy Link

@eliykat commented on GitHub (Apr 29, 2021):

Thanks for reporting this issue. Autofill problems can affect different sites, apps, or devices, and we’re working on improving this feature. To help us track and analyze affected sites, please lodge a report using the Google Form mentioned in this issue: #1389. Please also direct any discussion or questions to that issue. This issue will now be closed.

@eliykat commented on GitHub (Apr 29, 2021): Thanks for reporting this issue. Autofill problems can affect different sites, apps, or devices, and we’re working on improving this feature. To help us track and analyze affected sites, please lodge a report using the Google Form mentioned in this issue: #1389. Please also direct any discussion or questions to that issue. This issue will now be closed.
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
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#1147
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?