github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-05-07 03:23:29 -05:00
Code Issues 1.1k Packages Projects Releases 122 Wiki Activity

[GH-ISSUE #562] Autofill Chrome Android not working #26685

New Issue
Closed
opened 2026-04-18 09:56:54 -05:00 by GiteaMirror · 12 comments
GiteaMirror commented 2026-04-18 09:56:54 -05:00
Owner
Copy Link

Originally created by @sjtinsley83 on GitHub (Jul 18, 2019).
Original GitHub issue: https://github.com/bitwarden/android/issues/562

I am a new user of BitWarden. I want to used the autofill on my phone. I have enabled The autofill service but it doesn't work. Chrome is up to date and Android is version 9. Can someone help.

Originally created by @sjtinsley83 on GitHub (Jul 18, 2019). Original GitHub issue: https://github.com/bitwarden/android/issues/562 I am a new user of BitWarden. I want to used the autofill on my phone. I have enabled The autofill service but it doesn't work. Chrome is up to date and Android is version 9. Can someone help.
GiteaMirror commented 2026-04-18 09:56:54 -05:00
Author
Owner
Copy Link

@kspearrin commented on GitHub (Jul 19, 2019):

In chrome, navigate to "chrome://flags" and make sure autofill accessibility settings are turned on. Then restart and try again.

<!-- gh-comment-id:513061945 --> @kspearrin commented on GitHub (Jul 19, 2019): In chrome, navigate to "chrome://flags" and make sure autofill accessibility settings are turned on. Then restart and try again.
GiteaMirror commented 2026-04-18 09:56:55 -05:00
Author
Owner
Copy Link

@sjtinsley83 commented on GitHub (Jul 19, 2019):

Unfortunately, that doesn't work. If I used the accessibility autofill mode it works, but it would like to use the better autofill framework that is in Android. It appears there are quite a few people experiencing the same issue.

<!-- gh-comment-id:513290183 --> @sjtinsley83 commented on GitHub (Jul 19, 2019): Unfortunately, that doesn't work. If I used the accessibility autofill mode it works, but it would like to use the better autofill framework that is in Android. It appears there are quite a few people experiencing the same issue.
GiteaMirror commented 2026-04-18 09:56:56 -05:00
Author
Owner
Copy Link

@niikoo commented on GitHub (Jul 30, 2019):

+1

The experience is very unstable. Mostly resolved by restating the browser though. But that's not a good solution.

Don't know if this error from the logcat helps:

07-30 06:30:25.613  1508  1508 E AutofillManagerServiceImpl: Bad AutofillService name: com.x8bit.bitwarden/com.x8bit.bitwarden.Autofill.AutofillService
<!-- gh-comment-id:516540017 --> @niikoo commented on GitHub (Jul 30, 2019): +1 The experience is very unstable. Mostly resolved by restating the browser though. But that's not a good solution. Don't know if this error from the logcat helps: ``` 07-30 06:30:25.613 1508 1508 E AutofillManagerServiceImpl: Bad AutofillService name: com.x8bit.bitwarden/com.x8bit.bitwarden.Autofill.AutofillService ```
GiteaMirror commented 2026-04-18 09:56:56 -05:00
Author
Owner
Copy Link

@tiavision commented on GitHub (Aug 5, 2019):

Same here, but now it got even worse, not sure if the latest update of Chrome or Bitwarden broke it but now it does not even find the credentials anymore and I have to manually search for it. While still having the issue that I have to restart the browser. As a workaround I switched to the old autofill service

<!-- gh-comment-id:518362743 --> @tiavision commented on GitHub (Aug 5, 2019): Same here, but now it got even worse, not sure if the latest update of Chrome or Bitwarden broke it but now it does not even find the credentials anymore and I have to manually search for it. While still having the issue that I have to restart the browser. As a workaround I switched to the old autofill service
GiteaMirror commented 2026-04-18 09:56:56 -05:00
Author
Owner
Copy Link

@niikoo commented on GitHub (Aug 5, 2019):

@TimHeinrich I got the same problem. "com.android.chrome" is the identifier, not the webpage anymore.. Suddenly happened after the latest update. Version 2.2.0

Logcat filtered by 'bitwarden':

---- 5 Aug 2019 21:24:17 ----

08-05 16:20:35.619   830   942 W SurfaceFlinger: Attempting to set client state on removed layer: Surface(name=AppWindowToken{b4d7b14 token=Token{b789167 ActivityRecord{5f19126 u0 com.x8bit.bitwarden/.MainActivity t83892}}})/@0xe8a745e - animation-leash#0

08-05 16:20:35.620   830   942 W SurfaceFlinger: Attempting to destroy on removed layer: Surface(name=AppWindowToken{b4d7b14 token=Token{b789167 ActivityRecord{5f19126 u0 com.x8bit.bitwarden/.MainActivity t83892}}})/@0xe8a745e - animation-leash#0

08-05 18:30:45.926  8120  8120 W monodroid: Trying to load sgen from: /data/app/com.x8bit.bitwarden-hdIuKbGsxc0vcxMCcbAXvw==/lib/arm64/libmonosgen-2.0.so

08-05 19:19:26.928 17526 17526 W monodroid: Trying to load sgen from: /data/app/com.x8bit.bitwarden-hdIuKbGsxc0vcxMCcbAXvw==/lib/arm64/libmonosgen-2.0.so

08-05 21:20:11.884  1316 12552 E ActivityTrigger: activityStartTrigger: not whiteListedcom.x8bit.bitwarden/com.x8bit.bitwarden.MainActivity/2059

08-05 21:20:11.885  1316 12552 E ActivityTrigger: activityResumeTrigger: not whiteListedcom.x8bit.bitwarden/com.x8bit.bitwarden.MainActivity/2059

08-05 21:20:11.937  1316 13748 E ActivityTrigger: activityResumeTrigger: not whiteListedcom.x8bit.bitwarden/com.x8bit.bitwarden.MainActivity/2059

08-05 21:20:21.035  1316  1410 W ActivityManager: Activity pause timeout for ActivityRecord{f9497da u0 com.x8bit.bitwarden/.MainActivity t83950}

08-05 21:20:23.986 17526 17526 E Choreographer: skip doframe for com.x8bit.bitwarden

08-05 21:20:30.467  1316  2958 E ActivityTrigger: activityResumeTrigger: not whiteListedcom.x8bit.bitwarden/com.x8bit.bitwarden.MainActivity/2059

08-05 21:20:30.506  1316 13748 E ActivityTrigger: activityResumeTrigger: not whiteListedcom.x8bit.bitwarden/com.x8bit.bitwarden.MainActivity/2059

08-05 21:20:30.525 17526 17526 E Choreographer: skip doframe for com.x8bit.bitwarden

08-05 21:20:32.649 17526 17526 E Choreographer: skip doframe for com.x8bit.bitwarden

08-05 21:20:32.686   830   942 W SurfaceFlinger: Attempting to set client state on removed layer: com.x8bit.bitwarden/com.x8bit.bitwarden.MainActivity#0

08-05 21:20:32.686   830   942 W SurfaceFlinger: Attempting to destroy on removed layer: com.x8bit.bitwarden/com.x8bit.bitwarden.MainActivity#0

08-05 21:20:32.692   830   942 W SurfaceFlinger: Attempting to set client state on removed layer: com.x8bit.bitwarden/com.x8bit.bitwarden.MainActivity#0

08-05 21:20:32.692   830   942 W SurfaceFlinger: Attempting to destroy on removed layer: com.x8bit.bitwarden/com.x8bit.bitwarden.MainActivity#0

08-05 21:20:32.700 17526 17526 E Choreographer: skip doframe for com.x8bit.bitwarden

08-05 21:21:04.954  1316 12334 E ActivityTrigger: activityResumeTrigger: not whiteListedcom.x8bit.bitwarden/com.x8bit.bitwarden.MainActivity/2059

08-05 21:21:04.988  1316  2787 E ActivityTrigger: activityResumeTrigger: not whiteListedcom.x8bit.bitwarden/com.x8bit.bitwarden.MainActivity/2059

08-05 21:21:04.998 17526 17526 E Choreographer: skip doframe for com.x8bit.bitwarden

08-05 21:21:13.523  1316 12334 W AppOps  : Bad call: specified package com.x8bit.bitwarden under uid 99910124 but it is really 10124

08-05 21:21:13.534  1316 12334 W AppOps  : Bad call: specified package com.x8bit.bitwarden under uid 99910124 but it is really 10124

08-05 21:21:13.709  1316 12552 W AppOps  : Bad call: specified package com.x8bit.bitwarden under uid 99910124 but it is really 10124

08-05 21:21:13.711  1316 12334 W AppOps  : Bad call: specified package com.x8bit.bitwarden under uid 99910124 but it is really 10124

08-05 21:21:13.723  1316 12334 W AppOps  : Bad call: specified package com.x8bit.bitwarden under uid 99910124 but it is really 10124

08-05 21:21:13.818  1316 12552 W AppOps  : Bad call: specified package com.x8bit.bitwarden under uid 99910124 but it is really 10124

08-05 21:21:14.103 14749 14749 E AppInfoDashboard: Package: com.x8bit.bitwarden not found for user: 10

08-05 21:21:14.103 14749 14749 E AppInfoDashboard: Package: com.x8bit.bitwarden not found for user: 12

08-05 21:22:22.205  1316  2787 E ActivityTrigger: activityStartTrigger: not whiteListedcom.x8bit.bitwarden/com.x8bit.bitwarden.MainActivity/2059

08-05 21:22:22.206  1316  2787 E ActivityTrigger: activityResumeTrigger: not whiteListedcom.x8bit.bitwarden/com.x8bit.bitwarden.MainActivity/2059

08-05 21:22:22.254  1316  2787 E ActivityTrigger: activityResumeTrigger: not whiteListedcom.x8bit.bitwarden/com.x8bit.bitwarden.MainActivity/2059

08-05 21:22:24.203 17526 17526 E Choreographer: skip doframe for com.x8bit.bitwarden

08-05 21:22:24.392   830  3497 W SurfaceFlinger: Attempting to set client state on removed layer: com.x8bit.bitwarden/com.x8bit.bitwarden.MainActivity#0

08-05 21:22:24.392   830  3497 W SurfaceFlinger: Attempting to destroy on removed layer: com.x8bit.bitwarden/com.x8bit.bitwarden.MainActivity#0

08-05 21:22:24.397   830  3497 W SurfaceFlinger: Attempting to set client state on removed layer: com.x8bit.bitwarden/com.x8bit.bitwarden.MainActivity#0

08-05 21:22:24.397   830  3497 W SurfaceFlinger: Attempting to destroy on removed layer: com.x8bit.bitwarden/com.x8bit.bitwarden.MainActivity#0

08-05 21:22:24.409 17526 17526 E Choreographer: skip doframe for com.x8bit.bitwarden

08-05 21:22:24.820 17526 17526 E Choreographer: skip doframe for com.x8bit.bitwarden

08-05 21:22:53.157  1316 12540 E ActivityTrigger: activityStartTrigger: not whiteListedcom.x8bit.bitwarden/com.x8bit.bitwarden.MainActivity/2059

08-05 21:22:53.158  1316 12540 E ActivityTrigger: activityResumeTrigger: not whiteListedcom.x8bit.bitwarden/com.x8bit.bitwarden.MainActivity/2059

08-05 21:22:53.206  1316 12540 E ActivityTrigger: activityResumeTrigger: not whiteListedcom.x8bit.bitwarden/com.x8bit.bitwarden.MainActivity/2059

08-05 21:22:54.495   830  3497 W SurfaceFlinger: Attempting to set client state on removed layer: com.x8bit.bitwarden/com.x8bit.bitwarden.MainActivity#0

08-05 21:22:54.495   830  3497 W SurfaceFlinger: Attempting to destroy on removed layer: com.x8bit.bitwarden/com.x8bit.bitwarden.MainActivity#0

08-05 21:22:54.499   830   942 W SurfaceFlinger: Attempting to set client state on removed layer: com.x8bit.bitwarden/com.x8bit.bitwarden.MainActivity#0

08-05 21:22:54.500   830   942 W SurfaceFlinger: Attempting to destroy on removed layer: com.x8bit.bitwarden/com.x8bit.bitwarden.MainActivity#0

08-05 21:22:54.510 17526 17526 E Choreographer: skip doframe for com.x8bit.bitwarden

08-05 21:22:55.111 17526 17526 E Choreographer: skip doframe for com.x8bit.bitwarden

08-05 21:22:56.126 17526 17526 E Choreographer: skip doframe for com.x8bit.bitwarden

---- 5 Aug 2019 21:24:17 ----

Filtered on 'AutofillManagerServiceImpl:

---- 5 Aug 2019 21:31:38 ----

08-05 20:32:40.861  1316  2499 W AutofillManagerServiceImpl: cancelSessionLocked(): no session for 545655315(10090)

08-05 21:21:07.977  1316  2958 W AutofillManagerServiceImpl: cancelSessionLocked(): no session for 605620569(10124)

08-05 21:21:28.482  1316 12335 W AutofillManagerServiceImpl: cancelSessionLocked(): no session for 873985422(10291)

08-05 21:27:44.986  1316 19362 W AutofillManagerServiceImpl: cancelSessionLocked(): no session for -1910492369(10291)

---- 5 Aug 2019 21:31:38 ----
<!-- gh-comment-id:518364762 --> @niikoo commented on GitHub (Aug 5, 2019): @TimHeinrich I got the same problem. "com.android.chrome" is the identifier, not the webpage anymore.. Suddenly happened after the latest update. Version 2.2.0 Logcat filtered by 'bitwarden': ``` ---- 5 Aug 2019 21:24:17 ---- 08-05 16:20:35.619 830 942 W SurfaceFlinger: Attempting to set client state on removed layer: Surface(name=AppWindowToken{b4d7b14 token=Token{b789167 ActivityRecord{5f19126 u0 com.x8bit.bitwarden/.MainActivity t83892}}})/@0xe8a745e - animation-leash#0 08-05 16:20:35.620 830 942 W SurfaceFlinger: Attempting to destroy on removed layer: Surface(name=AppWindowToken{b4d7b14 token=Token{b789167 ActivityRecord{5f19126 u0 com.x8bit.bitwarden/.MainActivity t83892}}})/@0xe8a745e - animation-leash#0 08-05 18:30:45.926 8120 8120 W monodroid: Trying to load sgen from: /data/app/com.x8bit.bitwarden-hdIuKbGsxc0vcxMCcbAXvw==/lib/arm64/libmonosgen-2.0.so 08-05 19:19:26.928 17526 17526 W monodroid: Trying to load sgen from: /data/app/com.x8bit.bitwarden-hdIuKbGsxc0vcxMCcbAXvw==/lib/arm64/libmonosgen-2.0.so 08-05 21:20:11.884 1316 12552 E ActivityTrigger: activityStartTrigger: not whiteListedcom.x8bit.bitwarden/com.x8bit.bitwarden.MainActivity/2059 08-05 21:20:11.885 1316 12552 E ActivityTrigger: activityResumeTrigger: not whiteListedcom.x8bit.bitwarden/com.x8bit.bitwarden.MainActivity/2059 08-05 21:20:11.937 1316 13748 E ActivityTrigger: activityResumeTrigger: not whiteListedcom.x8bit.bitwarden/com.x8bit.bitwarden.MainActivity/2059 08-05 21:20:21.035 1316 1410 W ActivityManager: Activity pause timeout for ActivityRecord{f9497da u0 com.x8bit.bitwarden/.MainActivity t83950} 08-05 21:20:23.986 17526 17526 E Choreographer: skip doframe for com.x8bit.bitwarden 08-05 21:20:30.467 1316 2958 E ActivityTrigger: activityResumeTrigger: not whiteListedcom.x8bit.bitwarden/com.x8bit.bitwarden.MainActivity/2059 08-05 21:20:30.506 1316 13748 E ActivityTrigger: activityResumeTrigger: not whiteListedcom.x8bit.bitwarden/com.x8bit.bitwarden.MainActivity/2059 08-05 21:20:30.525 17526 17526 E Choreographer: skip doframe for com.x8bit.bitwarden 08-05 21:20:32.649 17526 17526 E Choreographer: skip doframe for com.x8bit.bitwarden 08-05 21:20:32.686 830 942 W SurfaceFlinger: Attempting to set client state on removed layer: com.x8bit.bitwarden/com.x8bit.bitwarden.MainActivity#0 08-05 21:20:32.686 830 942 W SurfaceFlinger: Attempting to destroy on removed layer: com.x8bit.bitwarden/com.x8bit.bitwarden.MainActivity#0 08-05 21:20:32.692 830 942 W SurfaceFlinger: Attempting to set client state on removed layer: com.x8bit.bitwarden/com.x8bit.bitwarden.MainActivity#0 08-05 21:20:32.692 830 942 W SurfaceFlinger: Attempting to destroy on removed layer: com.x8bit.bitwarden/com.x8bit.bitwarden.MainActivity#0 08-05 21:20:32.700 17526 17526 E Choreographer: skip doframe for com.x8bit.bitwarden 08-05 21:21:04.954 1316 12334 E ActivityTrigger: activityResumeTrigger: not whiteListedcom.x8bit.bitwarden/com.x8bit.bitwarden.MainActivity/2059 08-05 21:21:04.988 1316 2787 E ActivityTrigger: activityResumeTrigger: not whiteListedcom.x8bit.bitwarden/com.x8bit.bitwarden.MainActivity/2059 08-05 21:21:04.998 17526 17526 E Choreographer: skip doframe for com.x8bit.bitwarden 08-05 21:21:13.523 1316 12334 W AppOps : Bad call: specified package com.x8bit.bitwarden under uid 99910124 but it is really 10124 08-05 21:21:13.534 1316 12334 W AppOps : Bad call: specified package com.x8bit.bitwarden under uid 99910124 but it is really 10124 08-05 21:21:13.709 1316 12552 W AppOps : Bad call: specified package com.x8bit.bitwarden under uid 99910124 but it is really 10124 08-05 21:21:13.711 1316 12334 W AppOps : Bad call: specified package com.x8bit.bitwarden under uid 99910124 but it is really 10124 08-05 21:21:13.723 1316 12334 W AppOps : Bad call: specified package com.x8bit.bitwarden under uid 99910124 but it is really 10124 08-05 21:21:13.818 1316 12552 W AppOps : Bad call: specified package com.x8bit.bitwarden under uid 99910124 but it is really 10124 08-05 21:21:14.103 14749 14749 E AppInfoDashboard: Package: com.x8bit.bitwarden not found for user: 10 08-05 21:21:14.103 14749 14749 E AppInfoDashboard: Package: com.x8bit.bitwarden not found for user: 12 08-05 21:22:22.205 1316 2787 E ActivityTrigger: activityStartTrigger: not whiteListedcom.x8bit.bitwarden/com.x8bit.bitwarden.MainActivity/2059 08-05 21:22:22.206 1316 2787 E ActivityTrigger: activityResumeTrigger: not whiteListedcom.x8bit.bitwarden/com.x8bit.bitwarden.MainActivity/2059 08-05 21:22:22.254 1316 2787 E ActivityTrigger: activityResumeTrigger: not whiteListedcom.x8bit.bitwarden/com.x8bit.bitwarden.MainActivity/2059 08-05 21:22:24.203 17526 17526 E Choreographer: skip doframe for com.x8bit.bitwarden 08-05 21:22:24.392 830 3497 W SurfaceFlinger: Attempting to set client state on removed layer: com.x8bit.bitwarden/com.x8bit.bitwarden.MainActivity#0 08-05 21:22:24.392 830 3497 W SurfaceFlinger: Attempting to destroy on removed layer: com.x8bit.bitwarden/com.x8bit.bitwarden.MainActivity#0 08-05 21:22:24.397 830 3497 W SurfaceFlinger: Attempting to set client state on removed layer: com.x8bit.bitwarden/com.x8bit.bitwarden.MainActivity#0 08-05 21:22:24.397 830 3497 W SurfaceFlinger: Attempting to destroy on removed layer: com.x8bit.bitwarden/com.x8bit.bitwarden.MainActivity#0 08-05 21:22:24.409 17526 17526 E Choreographer: skip doframe for com.x8bit.bitwarden 08-05 21:22:24.820 17526 17526 E Choreographer: skip doframe for com.x8bit.bitwarden 08-05 21:22:53.157 1316 12540 E ActivityTrigger: activityStartTrigger: not whiteListedcom.x8bit.bitwarden/com.x8bit.bitwarden.MainActivity/2059 08-05 21:22:53.158 1316 12540 E ActivityTrigger: activityResumeTrigger: not whiteListedcom.x8bit.bitwarden/com.x8bit.bitwarden.MainActivity/2059 08-05 21:22:53.206 1316 12540 E ActivityTrigger: activityResumeTrigger: not whiteListedcom.x8bit.bitwarden/com.x8bit.bitwarden.MainActivity/2059 08-05 21:22:54.495 830 3497 W SurfaceFlinger: Attempting to set client state on removed layer: com.x8bit.bitwarden/com.x8bit.bitwarden.MainActivity#0 08-05 21:22:54.495 830 3497 W SurfaceFlinger: Attempting to destroy on removed layer: com.x8bit.bitwarden/com.x8bit.bitwarden.MainActivity#0 08-05 21:22:54.499 830 942 W SurfaceFlinger: Attempting to set client state on removed layer: com.x8bit.bitwarden/com.x8bit.bitwarden.MainActivity#0 08-05 21:22:54.500 830 942 W SurfaceFlinger: Attempting to destroy on removed layer: com.x8bit.bitwarden/com.x8bit.bitwarden.MainActivity#0 08-05 21:22:54.510 17526 17526 E Choreographer: skip doframe for com.x8bit.bitwarden 08-05 21:22:55.111 17526 17526 E Choreographer: skip doframe for com.x8bit.bitwarden 08-05 21:22:56.126 17526 17526 E Choreographer: skip doframe for com.x8bit.bitwarden ---- 5 Aug 2019 21:24:17 ---- ``` Filtered on 'AutofillManagerServiceImpl: ``` ---- 5 Aug 2019 21:31:38 ---- 08-05 20:32:40.861 1316 2499 W AutofillManagerServiceImpl: cancelSessionLocked(): no session for 545655315(10090) 08-05 21:21:07.977 1316 2958 W AutofillManagerServiceImpl: cancelSessionLocked(): no session for 605620569(10124) 08-05 21:21:28.482 1316 12335 W AutofillManagerServiceImpl: cancelSessionLocked(): no session for 873985422(10291) 08-05 21:27:44.986 1316 19362 W AutofillManagerServiceImpl: cancelSessionLocked(): no session for -1910492369(10291) ---- 5 Aug 2019 21:31:38 ---- ```
GiteaMirror commented 2026-04-18 09:56:57 -05:00
Author
Owner
Copy Link

@kspearrin commented on GitHub (Aug 5, 2019):

We have not changed anything regarding autofill, so maybe there was a change in Chrome.

<!-- gh-comment-id:518434247 --> @kspearrin commented on GitHub (Aug 5, 2019): We have not changed anything regarding autofill, so maybe there was a change in Chrome.
GiteaMirror commented 2026-04-18 09:56:57 -05:00
Author
Owner
Copy Link

@krallus commented on GitHub (Aug 6, 2019):

I am also new to Bitwarden and a little thrown by this behaviour. Here's a way to consistently recreate the problem. I'm using a Google Pixel 3a. Android 9 (build PQ3B.190705.003). Chrome 76.0.3809.89 (last update July 30, 2019). Bitwarden 2.2.0 (last update Aug 2, 2019).

  1. Using Chrome in Android, browse to https://www.realtor.ca/
  2. Click on the person icon and then sign-in
  3. Click on the bitwarden notification (at top of Android screen)
  4. Screen shows "Items for realtor.ca" -- this is correct.
  5. Click on one of the fields and click "Auto-fill with Bitwarden"
  6. Screen shows "Items for com.android.chrome" -- *** this is incorrect ***
  7. Click the back button and press anywhere on the screen not on a field until the bitwarden notification re-appears back at the top of the screen
  8. Click that Bitwarden notification and it is now again showing, correctly, "Items for realtor.ca" (but not always consistently .. see below)

Note that sometimes clicking on the top Bitwarden notification will also show "Items for com.android.chrome", but clicking back and checking the notification again will get it to go back to showing "Items for realtor.ca".

Clicking on a field and "Auto-fill with Bitwarden" consistently shows "Items for com.android.chrome".

At no point does a load of the realtor.ca sign-in screen ever get auto-populated with the Bitwarden-stored credentials, but opening up the notification while it correctly shows "Items for realtor.ca" and clicking on the stored credentials entry does populate the fields with the credentials.

I have Android's auto-fill service set to Bitwarden. In Bitwarden's settings, both the "Auto-fill Service" and the "Auto-fill Accessibility Service" are showing as "Enabled". The latter's "Always Scan" option is enabled.

I hope this helps.

<!-- gh-comment-id:518817252 --> @krallus commented on GitHub (Aug 6, 2019): I am also new to Bitwarden and a little thrown by this behaviour. Here's a way to consistently recreate the problem. I'm using a Google Pixel 3a. Android 9 (build PQ3B.190705.003). Chrome 76.0.3809.89 (last update July 30, 2019). Bitwarden 2.2.0 (last update Aug 2, 2019). 1) Using Chrome in Android, browse to https://www.realtor.ca/ 2) Click on the person icon and then sign-in 3) Click on the bitwarden notification (at top of Android screen) 4) Screen shows "Items for realtor.ca" -- this is correct. 5) Click on one of the fields and click "Auto-fill with Bitwarden" 6) Screen shows "Items for com.android.chrome" -- *** this is incorrect *** 7) Click the back button and press anywhere on the screen *not* on a field until the bitwarden notification re-appears back at the top of the screen 8) Click that Bitwarden notification and it is now again showing, correctly, "Items for realtor.ca" (but not always consistently .. see below) Note that sometimes clicking on the top Bitwarden notification will also show "Items for com.android.chrome", but clicking back and checking the notification again will get it to go back to showing "Items for realtor.ca". Clicking on a field and "Auto-fill with Bitwarden" *consistently* shows "Items for com.android.chrome". At no point does a *load* of the realtor.ca sign-in screen ever get auto-populated with the Bitwarden-stored credentials, but opening up the notification while it correctly shows "Items for realtor.ca" and clicking on the stored credentials entry does populate the fields with the credentials. I have Android's auto-fill service set to Bitwarden. In Bitwarden's settings, both the "Auto-fill Service" and the "Auto-fill Accessibility Service" are showing as "Enabled". The latter's "Always Scan" option is enabled. I hope this helps.
GiteaMirror commented 2026-04-18 09:56:58 -05:00
Author
Owner
Copy Link

@ghost commented on GitHub (Aug 8, 2019):

I'm also having autofill issues again. It's actually starting to get super annoying with it breaking over and over...

<!-- gh-comment-id:519550654 --> @ghost commented on GitHub (Aug 8, 2019): I'm also having autofill issues again. It's actually starting to get super annoying with it breaking over and over...
GiteaMirror commented 2026-04-18 09:56:58 -05:00
Author
Owner
Copy Link

@kspearrin commented on GitHub (Aug 8, 2019):

@niikoo @DougParker1992 I just debugged the app and it appears that chrome is no longer sending the WebDomain property with their ViewNode objects. Therefore, I cannot detect the website of the autofill request when using the autofill service in Bitwarden. This appears to be a regression in Chrome. Other browsers, such as Firefox Focus, seem to still be working fine.

I am going to close this issue since we are tracking these various Chrome issues here: https://github.com/bitwarden/mobile/issues/489

<!-- gh-comment-id:519639771 --> @kspearrin commented on GitHub (Aug 8, 2019): @niikoo @DougParker1992 I just debugged the app and it appears that chrome is no longer sending the `WebDomain` property with their ViewNode objects. Therefore, I cannot detect the website of the autofill request when using the autofill service in Bitwarden. This appears to be a regression in Chrome. Other browsers, such as Firefox Focus, seem to still be working fine. I am going to close this issue since we are tracking these various Chrome issues here: https://github.com/bitwarden/mobile/issues/489
GiteaMirror commented 2026-04-18 09:56:59 -05:00
Author
Owner
Copy Link

@kspearrin commented on GitHub (Aug 9, 2019):

I just tested some other password manager apps and it appears to be an issue there too. I don't think there is anything we can do here.

<!-- gh-comment-id:519953432 --> @kspearrin commented on GitHub (Aug 9, 2019): I just tested some other password manager apps and it appears to be an issue there too. I don't think there is anything we can do here.
GiteaMirror commented 2026-04-18 09:56:59 -05:00
Author
Owner
Copy Link

@ghhv commented on GitHub (Aug 15, 2019):

Hi,
@kspearrin An FYI.. I just started with Bitwarden .. getting the same issue on Chrome - BW is only detecting com.android.chrome but funnily enough my Lastpass which is still installed still works OK. (How Lastpass is still auto-filling when it's no longer set as the auto fill is also curious.. but I'm getting both..)
So did a reboot since I had just installed BW.. behaviour was unchanged.
Disabled LastPass on Accessibility.. which stopped the LP fill.. but BW did nothing.. rebooted again..
BW is working again.. but again only matching com.android.chrome.
I have autofill and accessibility enabled for BW.
Running on Android 9 with Chrome 76.0.3809.111
Note: Auto-fill still works if I manually search for the login.
I wish you success!

<!-- gh-comment-id:521620990 --> @ghhv commented on GitHub (Aug 15, 2019): Hi, @kspearrin An FYI.. I just started with Bitwarden .. getting the same issue on Chrome - BW is only detecting com.android.chrome but funnily enough my Lastpass which is still installed still works OK. (How Lastpass is still auto-filling when it's no longer set as the auto fill is also curious.. but I'm getting both..) So did a reboot since I had just installed BW.. behaviour was unchanged. Disabled LastPass on Accessibility.. which stopped the LP fill.. but BW did nothing.. rebooted again.. BW is working again.. but again only matching com.android.chrome. I have autofill and accessibility enabled for BW. Running on Android 9 with Chrome 76.0.3809.111 Note: Auto-fill still works if I manually search for the login. I wish you success!
GiteaMirror commented 2026-04-18 09:57:00 -05:00
Author
Owner
Copy Link

@kspearrin commented on GitHub (Aug 15, 2019):

@ghhv That's because you are using the LastPass accessibility service. Bitwarden's accessibility service works fine as well.

<!-- gh-comment-id:521627262 --> @kspearrin commented on GitHub (Aug 15, 2019): @ghhv That's because you are using the LastPass accessibility service. Bitwarden's accessibility service works fine as well.
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#26685
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?