Auto fill not working anymore #2138

@bitwarden-bot commented on GitHub (Jan 17, 2025):

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

@bitwarden-bot commented on GitHub (Jan 17, 2025): Thank you for your report! We've added this to our internal board for review. ID: PM-17222

GiteaMirror commented

https://github.com/user-attachments/assets/c0277921-9861-4487-9e3e-37efcbe85ea6

@T00rk commented on GitHub (Jan 18, 2025):

As you can see, pressing the accessibilty button is disabling accessibility instead of showing Bitwarden

@T00rk commented on GitHub (Jan 18, 2025): https://github.com/user-attachments/assets/c0277921-9861-4487-9e3e-37efcbe85ea6 As you can see, pressing the accessibilty button is disabling accessibility instead of showing Bitwarden

GiteaMirror commented

@SergeantConfused commented on GitHub (Jan 18, 2025):

Hello @T00rk,

Thank you for this report. Just to make sure that you and I are on the same page, are you unable to perform autofill using Bitwarden at all at any webpage and/or application, or only at specific webpages and/or applications?

Thank you,

@SergeantConfused commented on GitHub (Jan 18, 2025): Hello @T00rk, Thank you for this report. Just to make sure that you and I are on the same page, are you unable to perform autofill using Bitwarden at all at any webpage and/or application, or only at specific webpages and/or applications? Thank you,

GiteaMirror commented

@T00rk commented on GitHub (Jan 19, 2025):

I'm not sure yet but it seems there is only happening on Brave Browser

@T00rk commented on GitHub (Jan 19, 2025): I'm not sure yet but it seems there is only happening on Brave Browser

GiteaMirror commented

@cw7035cw commented on GitHub (Jan 19, 2025):

I'm not sure if this is the same issue but accessibility-based auto fill has also stopped working for me since the update. I have enabled the service in Android settings but the setting in the app won't turn on

@cw7035cw commented on GitHub (Jan 19, 2025): I'm not sure if this is the same issue but accessibility-based auto fill has also stopped working for me since the update. I have enabled the service in Android settings but the setting in the app won't turn on

GiteaMirror commented

@sh00t3r commented on GitHub (Jan 20, 2025):

I have the same issue, i cant enable the accessibility button in the bitwarden settings. In my system settings the permission is granted. Iam using edge as browser on my Samsung and cant fill in passwords anymore

@sh00t3r commented on GitHub (Jan 20, 2025): I have the same issue, i cant enable the accessibility button in the bitwarden settings. In my system settings the permission is granted. Iam using edge as browser on my Samsung and cant fill in passwords anymore

GiteaMirror commented

@danielintempesta commented on GitHub (Jan 21, 2025):

Same issue. Brave (Android 15)

@danielintempesta commented on GitHub (Jan 21, 2025): Same issue. Brave (Android 15)

GiteaMirror commented

@Aashishkebab commented on GitHub (Jan 23, 2025):

I reported this same issue to the support team. They completely ghosted me after a while and are ignoring everything I send to them.

It works half the time and the other half it doesn't, it's inconsistent. Accessibility doesn't work properly. Quick Tile doesn't work properly. It's so broken, and has been for long enough that I'm switching to a different password manager. What a pity.

@Aashishkebab commented on GitHub (Jan 23, 2025): I reported this same issue to the support team. They completely ghosted me after a while and are ignoring everything I send to them. It works half the time and the other half it doesn't, it's inconsistent. Accessibility doesn't work properly. Quick Tile doesn't work properly. It's so broken, and has been for long enough that I'm switching to a different password manager. What a pity.

GiteaMirror commented

@owocado commented on GitHub (Jan 25, 2025):

same issue on version 2025.1.0 on Android 15 for me

@owocado commented on GitHub (Jan 25, 2025): same issue on version 2025.1.0 on Android 15 for me

GiteaMirror commented

@jydhthrshrhty commented on GitHub (Jan 31, 2025):

same issue with brave for me, also almost the same setup.

Brave
Florisboard
grapheneos
bitwarden

the autofill will work only from tiles.

@jydhthrshrhty commented on GitHub (Jan 31, 2025): same issue with brave for me, also almost the same setup. Brave Florisboard grapheneos bitwarden the autofill will work only from tiles.

GiteaMirror commented

@T00rk commented on GitHub (Feb 8, 2025):

Still not working after the new update

@T00rk commented on GitHub (Feb 8, 2025): Still not working after the new update

GiteaMirror commented

@jydhthrshrhty commented on GitHub (Feb 11, 2025):

Still not working after the new update

I confirm. Had to use the Autofill tile to write this comment.

Hope it is in there priority to fix this issue.

@jydhthrshrhty commented on GitHub (Feb 11, 2025): > Still not working after the new update I confirm. Had to use the Autofill tile to write this comment. Hope it is in there priority to fix this issue.

GiteaMirror commented

@Aashishkebab commented on GitHub (Feb 11, 2025):

Still not working after the new update

I confirm. Had to use the Autofill tile to write this comment.

Hope it is in there priority to fix this issue.

I don't think they care, the support team is horrendous as well. The rating on the Play Store keeps dropping every few days 😂.

@Aashishkebab commented on GitHub (Feb 11, 2025): > > Still not working after the new update > > I confirm. Had to use the Autofill tile to write this comment. > > Hope it is in there priority to fix this issue. I don't think they care, the support team is horrendous as well. The rating on the Play Store keeps dropping every few days 😂.

GiteaMirror commented

@dwbit commented on GitHub (Feb 12, 2025):

Thanks for your patience everyone, a fix for the accessibility issue will be available shortly.

https://github.com/bitwarden/android/pull/4644

@dwbit commented on GitHub (Feb 12, 2025): Thanks for your patience everyone, a fix for the accessibility issue will be available shortly. - https://github.com/bitwarden/android/pull/4644

GiteaMirror commented

@jaymzh commented on GitHub (Feb 12, 2025):

I came here to report the same issue.

Bitwarden often doesn't show up in the keyboard auto fill for passwords.

Most recent example is the evite app.

So I enabled the accessibility overlay button, and nothing happens when I tap it.

@jaymzh commented on GitHub (Feb 12, 2025): I came here to report the same issue. Bitwarden often doesn't show up in the keyboard auto fill for passwords. Most recent example is the evite app. So I enabled the accessibility overlay button, and nothing happens when I tap it.

GiteaMirror commented

@T00rk commented on GitHub (Feb 28, 2025):

No update ?

@T00rk commented on GitHub (Feb 28, 2025): No update ?

GiteaMirror commented

@dwbit commented on GitHub (Feb 28, 2025):

The fix for the quick tile action will be included in the release starting to roll out next week, thanks for your patience!

@dwbit commented on GitHub (Feb 28, 2025): The fix for the quick tile action will be included in the release starting to roll out next week, thanks for your patience!

GiteaMirror commented

@jaymzh commented on GitHub (Feb 28, 2025):

Thanks!

@jaymzh commented on GitHub (Feb 28, 2025): Thanks!

GiteaMirror commented

@T00rk commented on GitHub (Mar 10, 2025):

Update just came out. Still not working on brave. Nothing changed.
When I setup an accessibility shortcut, clicking the shortcut enables or disables accessibility. I think it's supposed to open bitwarden application instead

@T00rk commented on GitHub (Mar 10, 2025): Update just came out. Still not working on brave. Nothing changed. When I setup an accessibility shortcut, clicking the shortcut enables or disables accessibility. I think it's supposed to open bitwarden application instead

GiteaMirror commented

@cw7035cw commented on GitHub (Mar 10, 2025):

Update just came out. Still not working on brave. Nothing changed.
When I setup an accessibility shortcut, clicking the shortcut enables or disables accessibility. I think it's supposed to open bitwarden application instead

This is the intended behavior on Android and not something the bitwarden devs can change. Bitwarden uses an accessibility service to display its own button where information can be filled in. The accessibility button feature of android enables and disables that service, and works the same way for any app using that feature.

If you leave bitwarden's accessibility service enabled, do prompts appear to auto fill saved passwords in apps that normally wouldn't? This is the part the devs need to fix

@cw7035cw commented on GitHub (Mar 10, 2025): > Update just came out. Still not working on brave. Nothing changed. > When I setup an accessibility shortcut, clicking the shortcut enables or disables accessibility. I think it's supposed to open bitwarden application instead This is the intended behavior on Android and not something the bitwarden devs can change. Bitwarden uses an accessibility service to display its own button where information can be filled in. The accessibility button feature of android enables and disables that service, and works the same way for any app using that feature. If you leave bitwarden's accessibility service enabled, do prompts appear to auto fill saved passwords in apps that normally wouldn't? This is the part the devs need to fix

GiteaMirror commented

@jydhthrshrhty commented on GitHub (Mar 10, 2025):

Nothing changed, still using Autofill tile for now

@jydhthrshrhty commented on GitHub (Mar 10, 2025): Nothing changed, still using Autofill tile for now

GiteaMirror commented

@T00rk commented on GitHub (Mar 10, 2025):

Update just came out. Still not working on brave. Nothing changed.
When I setup an accessibility shortcut, clicking the shortcut enables or disables accessibility. I think it's supposed to open bitwarden application instead

This is the intended behavior on Android and not something the bitwarden devs can change. Bitwarden uses an accessibility service to display its own button where information can be filled in. The accessibility button feature of android enables and disables that service, and works the same way for any app using that feature.

If you leave bitwarden's accessibility service enabled, do prompts appear to auto fill saved passwords in apps that normally wouldn't? This is the part the devs need to fix

Bitwarden autofill seems to work with every app except Brave Browser

@T00rk commented on GitHub (Mar 10, 2025): > > Update just came out. Still not working on brave. Nothing changed. > > When I setup an accessibility shortcut, clicking the shortcut enables or disables accessibility. I think it's supposed to open bitwarden application instead > > This is the intended behavior on Android and not something the bitwarden devs can change. Bitwarden uses an accessibility service to display its own button where information can be filled in. The accessibility button feature of android enables and disables that service, and works the same way for any app using that feature. > > If you leave bitwarden's accessibility service enabled, do prompts appear to auto fill saved passwords in apps that normally wouldn't? This is the part the devs need to fix Bitwarden autofill seems to work with every app except Brave Browser

GiteaMirror commented

@Aashishkebab commented on GitHub (Mar 17, 2025):

Update just came out. Still not working on brave. Nothing changed.
When I setup an accessibility shortcut, clicking the shortcut enables or disables accessibility. I think it's supposed to open bitwarden application instead

This is the intended behavior on Android and not something the bitwarden devs can change. Bitwarden uses an accessibility service to display its own button where information can be filled in. The accessibility button feature of android enables and disables that service, and works the same way for any app using that feature.

If you leave bitwarden's accessibility service enabled, do prompts appear to auto fill saved passwords in apps that normally wouldn't? This is the part the devs need to fix

This is incorrect. It used to work correctly, but now the accessibility service doesn't work at all.

App developers can choose what quick settings tiles do. It used to open the app and suggest Autofill for the previous screen, used when it wouldn't show up automatically.

Now, it only works sometimes, and it's buggy. The developers must have introduced at least 999 bugs with the major completely unnecessary overhaul.

@Aashishkebab commented on GitHub (Mar 17, 2025): > > Update just came out. Still not working on brave. Nothing changed. > > When I setup an accessibility shortcut, clicking the shortcut enables or disables accessibility. I think it's supposed to open bitwarden application instead > > This is the intended behavior on Android and not something the bitwarden devs can change. Bitwarden uses an accessibility service to display its own button where information can be filled in. The accessibility button feature of android enables and disables that service, and works the same way for any app using that feature. > > If you leave bitwarden's accessibility service enabled, do prompts appear to auto fill saved passwords in apps that normally wouldn't? This is the part the devs need to fix This is incorrect. It used to work correctly, but now the accessibility service doesn't work at all. App developers can choose what quick settings tiles do. It used to open the app and suggest Autofill for the previous screen, used when it wouldn't show up automatically. Now, it only works sometimes, and it's buggy. The developers must have introduced at least 999 bugs with the major completely unnecessary overhaul.

GiteaMirror commented

@linucksrox commented on GitHub (Mar 18, 2025):

I agree, this doesn't seem to make sense. This worked previously on Android 15, so it sounds wrong to now be told this can't be made to work anymore. Clarification would be greatly appreciated!

Also I can confirm, autofill through the keyboard works great on all apps except Brave. Should we open a new issue for that one at this point?

@dwbit can someone from the dev team please chime in?

@linucksrox commented on GitHub (Mar 18, 2025): I agree, this doesn't seem to make sense. This worked previously on Android 15, so it sounds wrong to now be told this can't be made to work anymore. Clarification would be greatly appreciated! Also I can confirm, autofill through the keyboard works great on all apps except Brave. Should we open a new issue for that one at this point? @dwbit can someone from the dev team please chime in?

GiteaMirror commented

@cw7035cw commented on GitHub (Mar 18, 2025):

I agree, this doesn't seem to make sense. This worked previously on Android 15, so it sounds wrong to now be told this can't be made to work anymore. Clarification would be greatly appreciated!

Also I can confirm, autofill through the keyboard works great on all apps except Brave. Should we open a new issue for that one at this point?

@dwbit can someone from the dev team please chime in?

I think people are confusing the quick settings tile with the accessibility button. The quick settings tile is supposed to activate autofill manually and is indeed broken, but I was talking about the accessibility button that can be turned on from accessibility settings on Android.

I also feel the need to mention that I don't work for or contribute to bitwarden. These views are my own and I agree that this should've been fixed months ago.

@cw7035cw commented on GitHub (Mar 18, 2025): > I agree, this doesn't seem to make sense. This worked previously on Android 15, so it sounds wrong to now be told this can't be made to work anymore. Clarification would be greatly appreciated! > > Also I can confirm, autofill through the keyboard works great on all apps except Brave. Should we open a new issue for that one at this point? > > @dwbit can someone from the dev team please chime in? I think people are confusing the quick settings tile with the accessibility button. The quick settings tile is supposed to activate autofill manually and is indeed broken, but I was talking about the accessibility button that can be turned on from accessibility settings on Android. I also feel the need to mention that I don't work for or contribute to bitwarden. These views are my own and I agree that this should've been fixed months ago.

GiteaMirror commented

@linucksrox commented on GitHub (Mar 18, 2025):

That's true. I'm actually referring to both the on screen overlay (maybe that's no longer possible?) and the keyboard auto suggest which pops up in the word suggestion area at the top of the keyboard.

I'm curious if we need to open another issue for this (these?) specifically.

@linucksrox commented on GitHub (Mar 18, 2025): That's true. I'm actually referring to both the on screen overlay (maybe that's no longer possible?) and the keyboard auto suggest which pops up in the word suggestion area at the top of the keyboard. I'm curious if we need to open another issue for this (these?) specifically.

GiteaMirror commented

@jydhthrshrhty commented on GitHub (Mar 18, 2025):

That's true. I'm actually referring to both the on screen overlay (maybe that's no longer possible?) and the keyboard auto suggest which pops up in the word suggestion area at the top of the keyboard.

I'm curious if we need to open another issue for this (these?) specifically.

You are correct; the original issue was about what you mentioned, and the 'tile' was the workaround. It seems they introduced a new issue with the latest version that affects the 'tile' workaround.

The new issue is that you sometimes have to turn 'Use Accessibility' off and back on to get 'tile' working.

to make thing clear to the dev team, the issue is only in Brave browser with GrapheneOS and most likely firmwares based on AOSP android 15

@jydhthrshrhty commented on GitHub (Mar 18, 2025): > That's true. I'm actually referring to both the on screen overlay (maybe that's no longer possible?) and the keyboard auto suggest which pops up in the word suggestion area at the top of the keyboard. > > I'm curious if we need to open another issue for this (these?) specifically. You are correct; the original issue was about what you mentioned, and the 'tile' was the workaround. It seems they introduced a new issue with the latest version that affects the 'tile' workaround. The new issue is that you sometimes have to turn 'Use Accessibility' off and back on to get 'tile' working. to make thing clear to the dev team, the issue is only in Brave browser with GrapheneOS and most likely firmwares based on AOSP android 15

GiteaMirror commented

@T00rk commented on GitHub (Mar 31, 2025):

Any news about this issue ?

Have you found what it could come from ?

@T00rk commented on GitHub (Mar 31, 2025): Any news about this issue ? Have you found what it could come from ?

GiteaMirror commented

@T00rk commented on GitHub (Apr 14, 2025):

...

@T00rk commented on GitHub (Apr 14, 2025): ...

GiteaMirror commented

@Aashishkebab commented on GitHub (Apr 14, 2025):

to make thing clear to the dev team, the issue is only in Brave browser with GrapheneOS

No. It happens on all browsers.

@Aashishkebab commented on GitHub (Apr 14, 2025): > to make thing clear to the dev team, the issue is only in Brave browser with GrapheneOS No. It happens on all browsers.

GiteaMirror commented

2025-11-26 23:09:18 -06:00

@T00rk commented on GitHub (Apr 15, 2025):

to make thing clear to the dev team, the issue is only in Brave browser with GrapheneOS

No. It happens on all browsers.

I temporarily moved from Brave to Iceraven (until BW is fixed) and I don't have this problem. Vivaldi also works well.
In my case this really only happens on Brave.

@T00rk commented on GitHub (Apr 15, 2025): > > to make thing clear to the dev team, the issue is only in Brave browser with GrapheneOS > > No. It happens on all browsers. I temporarily moved from Brave to Iceraven (until BW is fixed) and I don't have this problem. Vivaldi also works well. In my case this really only happens on Brave.

GiteaMirror commented

@Aashishkebab commented on GitHub (Apr 15, 2025):

to make thing clear to the dev team, the issue is only in Brave browser with GrapheneOS

No. It happens on all browsers.

I temporarily moved from Brave to Iceraven (until BW is fixed) and I don't have this problem. Vivaldi also works well. In my case this really only happens on Brave.

Vivaldi has issues for me and I've tested on Chrome and Firefox as well and documented it and even sent the videos to support (who are useless).

The issue isn't consistent.

@Aashishkebab commented on GitHub (Apr 15, 2025): > > > to make thing clear to the dev team, the issue is only in Brave browser with GrapheneOS > > > > > > No. It happens on all browsers. > > I temporarily moved from Brave to Iceraven (until BW is fixed) and I don't have this problem. Vivaldi also works well. In my case this really only happens on Brave. Vivaldi has issues for me and I've tested on Chrome and Firefox as well and documented it and even sent the videos to support (who are useless). The issue isn't consistent.

GiteaMirror commented

2025-11-26 23:09:18 -06:00

@SimonAkers commented on GitHub (Apr 27, 2025):

Bump on this, within the last week and without doing any software updates, Bitwarden will no longer autofill in any browser. Last system update was a month ago.

Galaxy S22+, OneUI 6.1, Android 14.

@SimonAkers commented on GitHub (Apr 27, 2025): Bump on this, within the last week and without doing any software updates, Bitwarden will no longer autofill in any browser. Last system update was a month ago. Galaxy S22+, OneUI 6.1, Android 14.

GiteaMirror commented

2025-11-26 23:09:18 -06:00

@Aashishkebab commented on GitHub (Apr 28, 2025):

Bump on this, within the last week and without doing any software updates, Bitwarden will no longer autofill in any browser. Last system update was a month ago.

Galaxy S22+, OneUI 6.1, Android 14.

They don't seem to care. The quick settings tile does help.

@Aashishkebab commented on GitHub (Apr 28, 2025): > Bump on this, within the last week and without doing any software updates, Bitwarden will no longer autofill in any browser. Last system update was a month ago. > > Galaxy S22+, OneUI 6.1, Android 14. They don't seem to care. The quick settings tile does help.

GiteaMirror commented

@T00rk commented on GitHub (Apr 28, 2025):

This issue has been opened for more than 3 months and is still not fixed. They stopped answering more than a month ago.

I think this will never get fixed. Bitwarden is more focused on changing the GUI and having a beautiful product than a working one.

@T00rk commented on GitHub (Apr 28, 2025): This issue has been opened for more than 3 months and is still not fixed. They stopped answering more than a month ago. I think this will never get fixed. Bitwarden is more focused on changing the GUI and having a beautiful product than a working one.

GiteaMirror commented

@fessmm commented on GitHub (Apr 28, 2025):

@SaintPatrck

@fessmm commented on GitHub (Apr 28, 2025): @SaintPatrck

GiteaMirror commented

https://github.com/user-attachments/assets/e064abd0-e7a1-4064-922b-b3c03b3565d1

@SaintPatrck commented on GitHub (Apr 30, 2025):

Hi all,

There are a few topics to cover, so let's jump right into it.

Regarding the video of the Accessibility Shortcut. As @cw7035cw stated in their comment, this is the intended behavior.¹ The purpose of Accessibility Shortcut is to provide a means to enable/disable an Accessibility Service. It does not trigger the Autofill action. That's not to say we can't make it trigger the autofill action, but that introduces UX nuances that are likely to cause more confusion than actually help.

You can verify this behavior, yourself, by disabling Accessibility, enabling the Accessibility Shortcut, tapping the Accessibility Shortcut, swiping down the notification bar and tapping the Bitwarden Autofill Quick Tile. You will see a dialog prompting you to enable the service. Conversely, if you disable Accessibility, tap the Accessibility Shortcut, then tap the Autofill Quick Tile from the notification bar, Bitwarden will launch if the foreground application is fillable and there are fillable fields detected. There are scenarios in which we skip the foreground application and we do not notify the user. In those cases it does appear to the user as though it is not working correctly, which leads me to...

The behavior of the Autofill Quick Tile. There is obviously room for improvement, as with all things. Now that I've dug into it, I do see a few places where we can improve messaging when the foreground application cannot be filled, and potentially mitigate some of the performance overhead incurred when Accessibility is enabled. We will be making those improvements in the near future. However, even without those improvements in place I'm seeing relatively consistent behavior when using the Autofill Quick Tile. Including with Brave browser. I've attached a video of Accessibility working in Chrome and Brave browser on a mealie.io container I quickly spun up so that I could also validate URI matching.

The inline autofill suggestions are a separate can of worms entirely. It would be incredibly helpful if a different issue was opened so that we could reduce some of the cross-talk on this thread and focus on inline suggestion issues in their own space.

I will leave this issue open until the improvements I mentioned are made. Until then, feel free to provide more details on Accessibility Quick Tile issues here.

Thank you all for your patience and being valuable members of our community. 🖖

Note

Emulator & build details used for testing

Version: 2025.3.0
📱 google sdk_gphone64_arm64 🤖 15@35 📦 dev

https://developer.android.com/guide/topics/ui/accessibility/service#shortcut ↩︎

@SaintPatrck commented on GitHub (Apr 30, 2025): Hi all, There are a few topics to cover, so let's jump right into it. Regarding the [video of the Accessibility Shortcut](https://github.com/bitwarden/android/issues/4586#issuecomment-2599483040). As @cw7035cw stated in their [comment](https://github.com/bitwarden/android/issues/4586#issuecomment-2711563898), this is the intended behavior.[^1] The purpose of Accessibility Shortcut is to provide a means to enable/disable an Accessibility Service. It does not **trigger** the Autofill action. That's not to say we _can't_ make it trigger the autofill action, but that introduces UX nuances that are likely to cause more confusion than actually help. You can verify this behavior, yourself, by **disabling** Accessibility, **enabling** the Accessibility Shortcut, tapping the Accessibility Shortcut, swiping down the notification bar and tapping the Bitwarden Autofill Quick Tile. You will see a dialog prompting you to enable the service. Conversely, if you **disable** Accessibility, tap the Accessibility Shortcut, then tap the Autofill Quick Tile from the notification bar, Bitwarden will launch if the foreground application is fillable and there are fillable fields detected. There are scenarios in which we skip the foreground application and we do not notify the user. In those cases it does appear to the user as though it is not working correctly, which leads me to... The behavior of the Autofill Quick Tile. There is obviously room for improvement, as with all things. Now that I've dug into it, I do see a few places where we can improve messaging when the foreground application cannot be filled, and potentially mitigate some of the performance overhead incurred when Accessibility is enabled. We will be making those improvements in the near future. However, even without those improvements in place I'm seeing relatively consistent behavior when using the Autofill Quick Tile. Including with Brave browser. I've attached a video of Accessibility working in Chrome and Brave browser on a mealie.io container I quickly spun up so that I could also validate URI matching. The inline autofill suggestions are a separate can of worms entirely. It would be incredibly helpful if a different issue was opened so that we could reduce some of the cross-talk on this thread and focus on inline suggestion issues in their own space. I will leave this issue open until the improvements I mentioned are made. Until then, feel free to provide more details on Accessibility Quick Tile issues here. Thank you all for your patience and being valuable members of our community. 🖖 > [!NOTE] > Emulator & build details used for testing > > Version: 2025.3.0 > 📱 google sdk_gphone64_arm64 🤖 15@35 📦 dev https://github.com/user-attachments/assets/e064abd0-e7a1-4064-922b-b3c03b3565d1 [^1]: https://developer.android.com/guide/topics/ui/accessibility/service#shortcut

GiteaMirror commented

@linucksrox commented on GitHub (May 1, 2025):

@SaintPatrck Thanks for the reply. I tried all the suggestions with the Quick Tile and that also doesn't work - it seems to be tied to whether inline autofill works or not, if Bitwarden does not detect that there are fillable fields then I guess it doesn't work, period. Your video example shows different behavior than what I (and I think many others) have been experiencing. Unfortunately the video evidence doesn't make it work on my device 😉

I will open a new issue for the inline autofill, maybe that's the ticket to unlock some of the inconsistencies we are seeing with the quick tile as well, who knows?

#5117

@linucksrox commented on GitHub (May 1, 2025): @SaintPatrck Thanks for the reply. I tried all the suggestions with the Quick Tile and that also doesn't work - it seems to be tied to whether inline autofill works or not, if Bitwarden does not detect that there are fillable fields then I guess it doesn't work, period. Your video example shows different behavior than what I (and I think many others) have been experiencing. Unfortunately the video evidence doesn't make it work on my device 😉 I will open a new issue for the inline autofill, maybe that's the ticket to unlock some of the inconsistencies we are seeing with the quick tile as well, who knows? #5117

GiteaMirror commented

@Aashishkebab commented on GitHub (May 1, 2025):

Hi all,

There are a few topics to cover, so let's jump right into it.

Regarding the video of the Accessibility Shortcut. As @cw7035cw stated in their comment, this is the intended behavior.1 The purpose of Accessibility Shortcut is to provide a means to enable/disable an Accessibility Service. It does not trigger the Autofill action. That's not to say we can't make it trigger the autofill action, but that introduces UX nuances that are likely to cause more confusion than actually help.

You can verify this behavior, yourself, by disabling Accessibility, enabling the Accessibility Shortcut, tapping the Accessibility Shortcut, swiping down the notification bar and tapping the Bitwarden Autofill Quick Tile. You will see a dialog prompting you to enable the service. Conversely, if you disable Accessibility, tap the Accessibility Shortcut, then tap the Autofill Quick Tile from the notification bar, Bitwarden will launch if the foreground application is fillable and there are fillable fields detected. There are scenarios in which we skip the foreground application and we do not notify the user. In those cases it does appear to the user as though it is not working correctly, which leads me to...

The behavior of the Autofill Quick Tile. There is obviously room for improvement, as with all things. Now that I've dug into it, I do see a few places where we can improve messaging when the foreground application cannot be filled, and potentially mitigate some of the performance overhead incurred when Accessibility is enabled. We will be making those improvements in the near future. However, even without those improvements in place I'm seeing relatively consistent behavior when using the Autofill Quick Tile. Including with Brave browser. I've attached a video of Accessibility working in Chrome and Brave browser on a mealie.io container I quickly spun up so that I could also validate URI matching.

The inline autofill suggestions are a separate can of worms entirely. It would be incredibly helpful if a different issue was opened so that we could reduce some of the cross-talk on this thread and focus on inline suggestion issues in their own space.

I will leave this issue open until the improvements I mentioned are made. Until then, feel free to provide more details on Accessibility Quick Tile issues here.

Thank you all for your patience and being valuable members of our community. 🖖

Note

Emulator & build details used for testing

Version: 2025.3.0 📱 google sdk_gphone64_arm64 🤖 15@35 📦 dev

Screen_recording_20250430_165154.mp4

Footnotes

https://developer.android.com/guide/topics/ui/accessibility/service#shortcut ↩

The AutoFill does not work consistently with the Tile. It'll only work if the inline shows up.

To be clear, this used to work perfectly before the massive completely unnecessary UI overhaul where everything broke.

@Aashishkebab commented on GitHub (May 1, 2025): > Hi all, > > There are a few topics to cover, so let's jump right into it. > > Regarding the [video of the Accessibility Shortcut](https://github.com/bitwarden/android/issues/4586#issuecomment-2599483040). As [@cw7035cw](https://github.com/cw7035cw) stated in their [comment](https://github.com/bitwarden/android/issues/4586#issuecomment-2711563898), this is the intended behavior.[1](#user-content-fn-1-ed37f7234f8b438c701f7376bc21d271) The purpose of Accessibility Shortcut is to provide a means to enable/disable an Accessibility Service. It does not **trigger** the Autofill action. That's not to say we _can't_ make it trigger the autofill action, but that introduces UX nuances that are likely to cause more confusion than actually help. > > You can verify this behavior, yourself, by **disabling** Accessibility, **enabling** the Accessibility Shortcut, tapping the Accessibility Shortcut, swiping down the notification bar and tapping the Bitwarden Autofill Quick Tile. You will see a dialog prompting you to enable the service. Conversely, if you **disable** Accessibility, tap the Accessibility Shortcut, then tap the Autofill Quick Tile from the notification bar, Bitwarden will launch if the foreground application is fillable and there are fillable fields detected. There are scenarios in which we skip the foreground application and we do not notify the user. In those cases it does appear to the user as though it is not working correctly, which leads me to... > > The behavior of the Autofill Quick Tile. There is obviously room for improvement, as with all things. Now that I've dug into it, I do see a few places where we can improve messaging when the foreground application cannot be filled, and potentially mitigate some of the performance overhead incurred when Accessibility is enabled. We will be making those improvements in the near future. However, even without those improvements in place I'm seeing relatively consistent behavior when using the Autofill Quick Tile. Including with Brave browser. I've attached a video of Accessibility working in Chrome and Brave browser on a mealie.io container I quickly spun up so that I could also validate URI matching. > > The inline autofill suggestions are a separate can of worms entirely. It would be incredibly helpful if a different issue was opened so that we could reduce some of the cross-talk on this thread and focus on inline suggestion issues in their own space. > > I will leave this issue open until the improvements I mentioned are made. Until then, feel free to provide more details on Accessibility Quick Tile issues here. > > Thank you all for your patience and being valuable members of our community. 🖖 > > Note > > Emulator & build details used for testing > > Version: 2025.3.0 📱 google sdk_gphone64_arm64 🤖 15@35 📦 dev > > Screen_recording_20250430_165154.mp4 > ## Footnotes > 1. https://developer.android.com/guide/topics/ui/accessibility/service#shortcut [↩](#user-content-fnref-1-ed37f7234f8b438c701f7376bc21d271) The AutoFill does not work consistently with the Tile. It'll only work if the inline shows up. To be clear, this used to work perfectly before the massive completely unnecessary UI overhaul where everything broke.

GiteaMirror commented

@SimonAkers commented on GitHub (May 5, 2025):

I've been doing some deeper troubleshooting and made some discoveries that might be helpful.

My most interesting discovery is that whatever latest version of Android I'm on, the autofill button seems to be provided through your keyboard, instead of showing up as a button hovering near the input field like it used to. This seems to work fine using Samsung Keyboard. However, on Gboard, the button will not be made visible if you have disabled the Text correction -> Show suggestion strip option (aka the option which suggests what word you want to type next). See photos below.

It's not clear to me whether this is the new way that the Android autofill service functions, or if I just never saw this button on the keyboard because I use Gboard with text suggestions disabled. At the very least, this button does seem to work for me, although it doesn't show up in Gboard unless I turn on text suggestions (which I really dislike).

Samsung Keyboard with text suggestions DISABLED:

Gboard with text suggestions DISABLED:

Gboard with text suggestions ENABLED:

I also built from scratch and installed the latest main branch and the v2025.1.0 release and ran them on my device. Neither one worked as it used to, but it has worked as it used to since the native Android version was released.

I also installed the v2024.6.0 release APK, which appears to be the last version before the native Android release, and it also did not change anything. All this leads me to believe that this is an issue caused by a change in the Android API itself which has yet to be handled. This could be due to changes in OneUI (or insert your OS flavor here) specifically.

I did some poking around in logcat, the only notable thing that seemed to consistently occur was this debug message whenever I focused an input field:

2025-05-04 19:03:00.338  2380-2380  AutofillSession         system_server                        D  Service did not request to wait for delayed fill response.

I can't tell if this message is a boilerplate debug message, or if a delayed fill response is not being fulfilled. I messed about with setting the FLAG_DELAY_FILL flag and was able to get the debug message to go away, but I don't currently understand the source code enough to know if this is actually related in any meaningful way.

@SimonAkers commented on GitHub (May 5, 2025): I've been doing some deeper troubleshooting and made some discoveries that might be helpful. My most interesting discovery is that whatever latest version of Android I'm on, the autofill button seems to be provided through your keyboard, instead of showing up as a button hovering near the input field like it used to. This seems to work fine using Samsung Keyboard. However, on **_Gboard_**, the button will **not** be made visible if you have disabled the `Text correction -> Show suggestion strip` option (aka the option which suggests what word you want to type next). See photos below. It's not clear to me whether this is the new way that the Android autofill service functions, or if I just never saw this button on the keyboard because I use Gboard with text suggestions disabled. At the very least, this button does seem to work for me, although it doesn't show up in Gboard unless I turn on text suggestions (which I really dislike). Samsung Keyboard with text suggestions DISABLED: ![Image](https://github.com/user-attachments/assets/eabd4255-f18b-4836-9ec2-2d30b59fbf55) Gboard with text suggestions DISABLED: ![Image](https://github.com/user-attachments/assets/0d71e9a9-9b7d-4cd2-ac89-9b0dbff5a655) Gboard with text suggestions ENABLED: ![Image](https://github.com/user-attachments/assets/e0735f6d-388c-4086-8091-c06274f0dede) I also built from scratch and installed the latest `main` branch and the `v2025.1.0` release and ran them on my device. Neither one worked as it used to, but it *has* worked as it used to since the native Android version was released. I also installed the `v2024.6.0` release APK, which appears to be the last version before the native Android release, and it also did not change anything. All this leads me to believe that this is an issue caused by a change in the Android API itself which has yet to be handled. This could be due to changes in OneUI (or `insert your OS flavor here`) specifically. I did some poking around in logcat, the only notable thing that seemed to consistently occur was this debug message whenever I focused an input field: ``` 2025-05-04 19:03:00.338 2380-2380 AutofillSession system_server D Service did not request to wait for delayed fill response. ``` I can't tell if this message is a boilerplate debug message, or if a delayed fill response is not being fulfilled. I messed about with setting the [FLAG_DELAY_FILL](https://developer.android.com/reference/android/service/autofill/FillResponse#FLAG_DELAY_FILL) flag and was able to get the debug message to go away, but I don't currently understand the source code enough to know if this is actually related in any meaningful way.

GiteaMirror commented

@jydhthrshrhty commented on GitHub (May 5, 2025):

Dev and users seem to not understand why T00rk have opened this issue. If you do not have GrapheneOS and Brave browser open your own issue!!!

this post is about inline autofill not workimg in brave browser with GrapheneOS!!

that it, that all

@jydhthrshrhty commented on GitHub (May 5, 2025): Dev and users seem to not understand why T00rk have opened this issue. If you do not have GrapheneOS and Brave browser open your own issue!!! this post is about inline autofill not workimg in brave browser with GrapheneOS!! that it, that all

GiteaMirror commented

@linucksrox commented on GitHub (May 5, 2025):

@jydhthrshrhty I opened a separate issue the other day specifically for inline autofill on grapheneos with brave: #5117

@linucksrox commented on GitHub (May 5, 2025): @jydhthrshrhty I opened a separate issue the other day specifically for inline autofill on grapheneos with brave: #5117

GiteaMirror commented

@SimonAkers commented on GitHub (May 7, 2025):

Looks like my problem was indeed keyboard related. I cleared the Gboard cache, uninstalled and reinstalled it, and the problem is now fixed. Behavior is exactly as expected now, see image below.

Worth noting that I was in the beta version of Gboard, I have now reverted to the release version just to mitigate future issues. Not certain if the problem is only beta related, you have to leave beta and reinstall to get release version.

I also do apologize if this is "off topic" for this issue, though it seems pretty messy in here. Just sharing my findings to hopefully help someone else.

@SimonAkers commented on GitHub (May 7, 2025): Looks like my problem was indeed keyboard related. I cleared the Gboard cache, uninstalled and reinstalled it, and the problem is now fixed. Behavior is exactly as expected now, see image below. Worth noting that I was in the beta version of Gboard, I have now reverted to the release version just to mitigate future issues. Not certain if the problem is only beta related, you have to leave beta and reinstall to get release version. ![Screenshot_20250506_200457_Chrome.jpg](https://github.com/user-attachments/assets/4d077e82-784d-4dd4-a1aa-bb85d89797bf) *I also do apologize if this is "off topic" for this issue, though it seems pretty messy in here. Just sharing my findings to hopefully help someone else.*

GiteaMirror commented

@T00rk commented on GitHub (May 7, 2025):

Looks like my problem was indeed keyboard related. I cleared the Gboard cache, uninstalled and reinstalled it, and the problem is now fixed. Behavior is exactly as expected now, see image below.

Worth noting that I was in the beta version of Gboard, I have now reverted to the release version just to mitigate future issues. Not certain if the problem is only beta related, you have to leave beta and reinstall to get release version.

...

I also do apologize if this is "off topic" for this issue, though it seems pretty messy in here. Just sharing my findings to hopefully help someone else.

As I'm using Swiftkey I tried

cleaning swiftkey's cache (still no autofill on Brave)
uninstall swiftkey
install gboard (still no autofill on Brave)
reinstall swiftkey (still no autofill on Brave)

As I said in a previous comment I tried with Iceraven, Vivaldi and Firefox and all of them worked fine. I think if it were really keyboard related it wouldn't work with any browser.

@T00rk commented on GitHub (May 7, 2025): > Looks like my problem was indeed keyboard related. I cleared the Gboard cache, uninstalled and reinstalled it, and the problem is now fixed. Behavior is exactly as expected now, see image below. > > Worth noting that I was in the beta version of Gboard, I have now reverted to the release version just to mitigate future issues. Not certain if the problem is only beta related, you have to leave beta and reinstall to get release version. > > ... > > _I also do apologize if this is "off topic" for this issue, though it seems pretty messy in here. Just sharing my findings to hopefully help someone else._ As I'm using Swiftkey I tried - cleaning swiftkey's cache (still no autofill on Brave) - uninstall swiftkey - install gboard (still no autofill on Brave) - reinstall swiftkey (still no autofill on Brave) As I said in a previous comment I tried with Iceraven, Vivaldi and Firefox and all of them worked fine. I think if it were really keyboard related it wouldn't work with any browser.

GiteaMirror commented

https://github.com/brave/brave-browser/issues/36553#issuecomment-2555045732

@T00rk commented on GitHub (May 23, 2025):

This workaround works for me

@T00rk commented on GitHub (May 23, 2025): This workaround works for me https://github.com/brave/brave-browser/issues/36553#issuecomment-2555045732

GiteaMirror commented

@jydhthrshrhty commented on GitHub (May 23, 2025):

This workaround works for me

brave/brave-browser#36553 (comment)

getting this error

This site can’t be reached
The web page at brave://settings/ might be temporarily down or it may have moved permanently to a new web address.
ERR_INVALID_URL

@jydhthrshrhty commented on GitHub (May 23, 2025): > This workaround works for me > > [brave/brave-browser#36553 (comment)](https://github.com/brave/brave-browser/issues/36553#issuecomment-2555045732) getting this error This site can’t be reached The web page at brave://settings/ might be temporarily down or it may have moved permanently to a new web address. ERR_INVALID_URL

GiteaMirror commented

@jydhthrshrhty commented on GitHub (May 23, 2025):

BTW I use the best known settings for brave

Brave¶

Brave Shields & privacy > Block trackers & ads > Aggressive

Brave Shields & privacy > Always use secure connections > Enabled

Brave Shields & privacy > Block Fingerprinting > Strict

Brave Shields & privacy > Unstoppable Domains > Disabled

Brave Shields & privacy > Ethereum Name Service > Disabled

Brave Shields & privacy > Solana Name Service > Disabled

Brave Shields & privacy > IPFS Gateway > Disabled

Brave Shields & privacy > WebRTC IP handling policy > Disable non-proxied UDP

Brave Shields & privacy > Allow privacy-preserving product analytics > Disabled

Brave Shields & privacy > Automatically send diagnostic reports > Disabled

Brave Shields & privacy > Automatically send daily usage ping to Brave > Disabled

Brave News > Disabled

Brave Rewards > Show Ads when Brave is not in use > Disabled

Brave Wallet > Display Web3 notifications > Disabled

Appearance > Show Brave Rewards icon in address bar > Disabled

New Tab Page > Show Sponsored Images > Disabled

@jydhthrshrhty commented on GitHub (May 23, 2025): BTW I use the best known settings for brave Brave¶ Brave Shields & privacy > Block trackers & ads > Aggressive Brave Shields & privacy > Always use secure connections > Enabled Brave Shields & privacy > Block Fingerprinting > Strict Brave Shields & privacy > Unstoppable Domains > Disabled Brave Shields & privacy > Ethereum Name Service > Disabled Brave Shields & privacy > Solana Name Service > Disabled Brave Shields & privacy > IPFS Gateway > Disabled Brave Shields & privacy > WebRTC IP handling policy > Disable non-proxied UDP Brave Shields & privacy > Allow privacy-preserving product analytics > Disabled Brave Shields & privacy > Automatically send diagnostic reports > Disabled Brave Shields & privacy > Automatically send daily usage ping to Brave > Disabled Brave News > Disabled Brave Rewards > Show Ads when Brave is not in use > Disabled Brave Wallet > Display Web3 notifications > Disabled Appearance > Show Brave Rewards icon in address bar > Disabled New Tab Page > Show Sponsored Images > Disabled

GiteaMirror commented

2025-11-26 23:09:22 -06:00

@T00rk commented on GitHub (May 23, 2025):

This workaround works for me
brave/brave-browser#36553 (comment)

getting this error

This site can’t be reached The web page at brave://settings/ might be temporarily down or it may have moved permanently to a new web address. ERR_INVALID_URL

You can reach brave settings using the brave browser's menu

@T00rk commented on GitHub (May 23, 2025): > > This workaround works for me > > [brave/brave-browser#36553 (comment)](https://github.com/brave/brave-browser/issues/36553#issuecomment-2555045732) > > getting this error > > This site can’t be reached The web page at brave://settings/ might be temporarily down or it may have moved permanently to a new web address. ERR_INVALID_URL You can reach brave settings using the brave browser's menu

GiteaMirror commented

@jydhthrshrhty commented on GitHub (May 23, 2025):

This workaround works for me
brave/brave-browser#36553 (comment)

getting this error
This site can’t be reached The web page at brave://settings/ might be temporarily down or it may have moved permanently to a new web address. ERR_INVALID_URL

You can reach brave settings using the brave browser's menu

thank you, but can't find it

@jydhthrshrhty commented on GitHub (May 23, 2025): > > > This workaround works for me > > > [brave/brave-browser#36553 (comment)](https://github.com/brave/brave-browser/issues/36553#issuecomment-2555045732) > > > > > > getting this error > > This site can’t be reached The web page at brave://settings/ might be temporarily down or it may have moved permanently to a new web address. ERR_INVALID_URL > > You can reach brave settings using the brave browser's menu thank you, but can't find it

GiteaMirror commented

2025-11-26 23:09:22 -06:00

@SaintPatrck commented on GitHub (May 28, 2025):

Closing this issue as it appears to be resolved once Brave settings are correct. Thank you all for the assistance and patience.

@SaintPatrck commented on GitHub (May 28, 2025): Closing this issue as it appears to be resolved once Brave settings are correct. Thank you all for the assistance and patience.

GiteaMirror commented

2025-11-26 23:09:22 -06:00

@Aashishkebab commented on GitHub (May 28, 2025):

Are you kidding me? THIS ISSUE IS NOT RESOLVED. This issue is not specific to Brave and this issue still is a major problem and annoyance.

I have issues every day on both Vivaldi and Chrome on Android. Heck, it just happened just now trying to log into GitHub.

Please reopen the issue or I'll have to file another one. Not to mention that workarounds do not count as an issue being fixed, that's terrible QA.

@Aashishkebab commented on GitHub (May 28, 2025): Are you kidding me? THIS ISSUE IS NOT RESOLVED. This issue is not specific to Brave and this issue still is a major problem and annoyance. I have issues every day on both Vivaldi and Chrome on Android. Heck, it just happened just now trying to log into GitHub. Please reopen the issue or I'll have to file another one. Not to mention that workarounds do not count as an issue being fixed, that's terrible QA.

GiteaMirror commented

@SaintPatrck commented on GitHub (May 28, 2025):

@Aashishkebab The author of this issue stated it only manifests with Brave and that has been resolved. The resolution may be referred to as a workaround here, but enabling those flags is the only way to make Brave invoke Bitwarden, and that is out of our control. If the autofill framework never sends Bitwarden a request, it cannot provide autofill suggestions. Please open a new GitHub issue with details about your experience and I'll be happy to investigate further.

@SaintPatrck commented on GitHub (May 28, 2025): @Aashishkebab The author of this issue stated it only manifests with Brave and that has been resolved. The resolution may be referred to as a workaround here, but enabling those flags is the only way to make Brave invoke Bitwarden, and that is out of our control. If the autofill framework never sends Bitwarden a request, it cannot provide autofill suggestions. Please open a new GitHub issue with details about your experience and I'll be happy to investigate further.

GiteaMirror commented

@Aashishkebab commented on GitHub (May 28, 2025):

@Aashishkebab The author of this issue stated it only manifests with Brave and that has been resolved. The resolution may be referred to as a workaround here, but enabling those flags is the only way to make Brave invoke Bitwarden, and that is out of our control. If the autofill framework never sends Bitwarden a request, it cannot provide autofill suggestions. Please open a new GitHub issue with details about your experience and I'll be happy to investigate further.

Alright. https://github.com/bitwarden/android/issues/5278 with video evidence.

@Aashishkebab commented on GitHub (May 28, 2025): > [@Aashishkebab](https://github.com/Aashishkebab) The author of this issue stated it only manifests with Brave and that has been resolved. The resolution may be referred to as a workaround here, but enabling those flags is the only way to make Brave invoke Bitwarden, and that is out of our control. If the autofill framework never sends Bitwarden a request, it cannot provide autofill suggestions. Please open a new GitHub issue with details about your experience and I'll be happy to investigate further. Alright. https://github.com/bitwarden/android/issues/5278 with video evidence.

GiteaMirror commented

@fotex commented on GitHub (May 31, 2025):

I had the same problem and cleaning cache of gboard app fixes it.

@fotex commented on GitHub (May 31, 2025): I had the same problem and cleaning cache of gboard app fixes it.

GiteaMirror commented