github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-03-09 11:44:41 -05:00
Code Issues 144 Packages Projects Releases 116 Wiki Activity

Accessibility auto-fill cannot be used with accessibility shortcuts #2047

New Issue
Closed
opened 2025-11-26 23:06:18 -06:00 by GiteaMirror · 14 comments
GiteaMirror commented 2025-11-26 23:06:18 -06:00
Owner
Copy Link

Originally created by @lucasmz-dev on GitHub (Nov 3, 2024).

Steps To Reproduce

  1. Enable accessibility auto-fill on Settings > Auto-fill
  2. Enable an accessibility shortcut for it, such as holding both volume keys to toggle it
  3. Leave Bitwarden and use the volume keys to disable and enable them
  4. Come back to Bitwarden and check if accessibility auto-fill works

Expected Result

Accessibility auto-fill should work despite being toggled using accessibility shortcuts.

Actual Result

Accessibility auto-fill breaks when accessibility shortcuts are used, and believes it is off when it is in fact on.

Screenshots or Videos

No response

Additional Context

This didn't happen on the xamarin app

Build Version

2024.10.2 - F-Droid variant from BW repo

What server are you connecting to?

Self-host

Self-host Server Version

vaultwarden

Environment Details

  • Device: Moto G52 "rhode"
  • Android: 14
  • OS: CalyxOS 5.11.2

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 (Nov 3, 2024). ### Steps To Reproduce 1. Enable accessibility auto-fill on Settings > Auto-fill 2. Enable an accessibility shortcut for it, such as holding both volume keys to toggle it 3. Leave Bitwarden and use the volume keys to disable and enable them 4. Come back to Bitwarden and check if accessibility auto-fill works ### Expected Result Accessibility auto-fill should work despite being toggled using accessibility shortcuts. ### Actual Result Accessibility auto-fill breaks when accessibility shortcuts are used, and believes it is off when it is in fact on. ### Screenshots or Videos _No response_ ### Additional Context This didn't happen on the xamarin app ### Build Version 2024.10.2 - F-Droid variant from BW repo ### What server are you connecting to? Self-host ### Self-host Server Version vaultwarden ### Environment Details - Device: Moto G52 "rhode" - Android: 14 - OS: CalyxOS 5.11.2 ### 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 app:password-managerbug labels 2025-11-26 23:06:18 -06:00
GiteaMirror commented 2025-11-26 23:06:19 -06:00
Author
Owner
Copy Link

@lucasmz-dev commented on GitHub (Nov 3, 2024):

I end up using it like this for security reasons, accessibility is naturally an invasive permission and it only becomes useful in certain situations, where I then end up using the volume keys to manually do it.

@lucasmz-dev commented on GitHub (Nov 3, 2024): I end up using it like this for security reasons, accessibility is naturally an invasive permission and it only becomes useful in certain situations, where I then end up using the volume keys to manually do it.
GiteaMirror commented 2025-11-26 23:06:19 -06:00
Author
Owner
Copy Link

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

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

@bitwarden-bot commented on GitHub (Nov 3, 2024): Thank you for your report! We've added this to our internal board for review. ID: PM-14435
GiteaMirror commented 2025-11-26 23:06:19 -06:00
Author
Owner
Copy Link

@BBGhub commented on GitHub (Nov 3, 2024):

Hi there!

Thank you for your report, it seems like it is a duplicate of this one https://github.com/bitwarden/android/issues/3595

If you wish to add any further information/screenshots/recordings etc., please feel free to do so at any time in there - our engineering team will be happy to review these.

Vaultwarden users, see this FAQ: https://bitwarden.com/help/hosting-faqs/#q-do-bitwarden-client-apps-support-non-official-servers

This issue will now be closed.

Thanks!

@BBGhub commented on GitHub (Nov 3, 2024): Hi there! Thank you for your report, it seems like it is a duplicate of this one https://github.com/bitwarden/android/issues/3595 If you wish to add any further information/screenshots/recordings etc., please feel free to do so at any time in there - our engineering team will be happy to review these. Vaultwarden users, see this FAQ: https://bitwarden.com/help/hosting-faqs/#q-do-bitwarden-client-apps-support-non-official-servers This issue will now be closed. Thanks!
GiteaMirror commented 2025-11-26 23:06:20 -06:00
Author
Owner
Copy Link

@lucasmz-dev commented on GitHub (Nov 3, 2024):

Hey I don't think this constitutes a duplicate.

@lucasmz-dev commented on GitHub (Nov 3, 2024): Hey I don't think this constitutes a duplicate.
GiteaMirror commented 2025-11-26 23:06:20 -06:00
Author
Owner
Copy Link

@fessmm commented on GitHub (Nov 4, 2024):

@BBGhub how is that a duplicate? pls explain

@fessmm commented on GitHub (Nov 4, 2024): @BBGhub how is that a duplicate? pls explain
GiteaMirror commented 2025-11-26 23:06:20 -06:00
Author
Owner
Copy Link

@differsthecat commented on GitHub (Nov 12, 2024):

Hello, I am on the engineering team at Bitwarden.

We looked at this and cannot reproduce this issue with the latest release. We have made a number of bug fixes that may have addressed this as a side effect; @lucasmz-dev can you try the latest release (2024.11.3) and see if it has been resolved?

I have reopened this until we can confirm. If you are still seeing it, we will continue investigating in engineering.
Thank you!

@differsthecat commented on GitHub (Nov 12, 2024): Hello, I am on the engineering team at Bitwarden. We looked at this and cannot reproduce this issue with the latest release. We have made a number of bug fixes that may have addressed this as a side effect; @lucasmz-dev can you try the latest release (2024.11.3) and see if it has been resolved? I have reopened this until we can confirm. If you are still seeing it, we will continue investigating in engineering. Thank you!
GiteaMirror commented 2025-11-26 23:06:20 -06:00
Author
Owner
Copy Link

@lucasmz-dev commented on GitHub (Nov 12, 2024):

Nice one fixing them other bugs! Unfortunately I can still reproduce this on the latest version.

@lucasmz-dev commented on GitHub (Nov 12, 2024): Nice one fixing them other bugs! Unfortunately I can still reproduce this on the latest version.
GiteaMirror commented 2025-11-26 23:06:20 -06:00
Author
Owner
Copy Link

@differsthecat commented on GitHub (Nov 13, 2024):

@lucasmz-dev Ah, that's unfortunate! We will keep investigating on our end, thank you.

@differsthecat commented on GitHub (Nov 13, 2024): @lucasmz-dev Ah, that's unfortunate! We will keep investigating on our end, thank you.
GiteaMirror commented 2025-11-26 23:06:20 -06:00
Author
Owner
Copy Link

@Bondog83 commented on GitHub (Dec 20, 2024):

I'm having same issue on galaxy S24

@Bondog83 commented on GitHub (Dec 20, 2024): I'm having same issue on galaxy S24
GiteaMirror commented 2025-11-26 23:06:21 -06:00
Author
Owner
Copy Link

@Bondog83 commented on GitHub (Jan 4, 2025):

Still occurring. When is this going to be resolved?

@Bondog83 commented on GitHub (Jan 4, 2025): Still occurring. When is this going to be resolved?
GiteaMirror commented 2025-11-26 23:06:21 -06:00
Author
Owner
Copy Link

@Bondog83 commented on GitHub (Jan 4, 2025):

Hello, I am on the engineering team at Bitwarden.

We looked at this and cannot reproduce this issue with the latest release. We have made a number of bug fixes that may have addressed this as a side effect; @lucasmz-dev can you try the latest release (2024.11.3) and see if it has been resolved?

I have reopened this until we can confirm. If you are still seeing it, we will continue investigating in engineering. Thank you!

This most up to date version on the play store is 2024.10.0.

@Bondog83 commented on GitHub (Jan 4, 2025): > Hello, I am on the engineering team at Bitwarden. > > We looked at this and cannot reproduce this issue with the latest release. We have made a number of bug fixes that may have addressed this as a side effect; @lucasmz-dev can you try the latest release (2024.11.3) and see if it has been resolved? > > I have reopened this until we can confirm. If you are still seeing it, we will continue investigating in engineering. Thank you! This most up to date version on the play store is 2024.10.0.
GiteaMirror commented 2025-11-26 23:06:21 -06:00
Author
Owner
Copy Link

@lucasmz-dev commented on GitHub (Jan 4, 2025):

@Bondog83 isn't that still the non-native app?

@lucasmz-dev commented on GitHub (Jan 4, 2025): @Bondog83 isn't that still the non-native app?
GiteaMirror commented 2025-11-26 23:06:21 -06:00
Author
Owner
Copy Link

@Bondog83 commented on GitHub (Jan 4, 2025):

@Bondog83 isn't that still the non-native app?

Not sure, guess Bitwarden refuses to update the app in the Play Store

@Bondog83 commented on GitHub (Jan 4, 2025): > @Bondog83 isn't that still the non-native app? Not sure, guess Bitwarden refuses to update the app in the Play Store
GiteaMirror commented 2025-11-26 23:06:21 -06:00
Author
Owner
Copy Link

@aj-rosado commented on GitHub (Mar 25, 2025):

We have made some changes on https://github.com/bitwarden/android/pull/4864 and https://github.com/bitwarden/android/pull/4756 that should fix this on next release!

Closing it for now, if the issues persists after next release let us know.

Thank you for your patience.

@aj-rosado commented on GitHub (Mar 25, 2025): We have made some changes on https://github.com/bitwarden/android/pull/4864 and https://github.com/bitwarden/android/pull/4756 that should fix this on next release! Closing it for now, if the issues persists after next release let us know. Thank you for your patience.
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#2047
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?