Accessibility auto-fill cannot be used with accessibility shortcuts

[lucasmz-dev]

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.

[lucasmz-dev]

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.

[bitwarden-bot]

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

[BBGhub]

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!

[lucasmz-dev]

Hey I don't think this constitutes a duplicate.

[fessmm]

@BBGhub how is that a duplicate? pls explain

[differsthecat]

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!

[lucasmz-dev]

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

[differsthecat]

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