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

Android app often needs two attempts to auto-fill #784

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

Originally created by @scotsman42 on GitHub (Jun 18, 2019).

Originally assigned to: @mpbw2 on GitHub.

Steps to re-produce

  1. Using Chrome on Android go to website such as https://myaccount.nytimes.com/auth/login
  2. Tap password field (no autofill is displayed)
  3. Open notifications and select Bitwarden Auto-fill Service
  4. select nytimes.com from "items for nytimes.com"
  5. returned to Chrome, form is not filled in
  6. open notifications and select Bitwarden Auto-fill Service
  7. select nytimes.com from "items for nytimes.com"
  8. returned to Chrome, form is now filled in.

Occurs for most sites, doesn't appear to be site specific.
Auto-fill Service: Enabled
Auto-fill Accessibility Service: Enabled

Bitwarden (Android) version 2.0.6 (1938)
Chrome 74.0.3729.149
Android 10; Pixel 3 Build/QPP4.190502.019,
Also re-producible on Android 9

Originally created by @scotsman42 on GitHub (Jun 18, 2019). Originally assigned to: @mpbw2 on GitHub. Steps to re-produce 1. Using Chrome on Android go to website such as https://myaccount.nytimes.com/auth/login 2. Tap password field (no autofill is displayed) 3. Open notifications and select Bitwarden Auto-fill Service 4. select nytimes.com from "items for nytimes.com" 5. returned to Chrome, form is not filled in 6. open notifications and select Bitwarden Auto-fill Service 4. select nytimes.com from "items for nytimes.com" 5. returned to Chrome, form is now filled in. Occurs for most sites, doesn't appear to be site specific. Auto-fill Service: Enabled Auto-fill Accessibility Service: Enabled Bitwarden (Android) version 2.0.6 (1938) Chrome 74.0.3729.149 Android 10; Pixel 3 Build/QPP4.190502.019, Also re-producible on Android 9
GiteaMirror commented 2025-11-26 22:29:11 -06:00
Author
Owner
Copy Link

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

After step 5, try tapping the password field on page again. Does it fill it then?

@kspearrin commented on GitHub (Jun 19, 2019): After step 5, try tapping the password field on page again. Does it fill it then?
GiteaMirror commented 2025-11-26 22:29:11 -06:00
Author
Owner
Copy Link

@mindrunner commented on GitHub (Oct 20, 2019):

Can confirm this, however in step 4, I always observe that I do not autofill for "sitename.com", but for "com.google.chrome". Or any other appid, depending on the chrome-version I am using. This happens with

  • chrome
  • chromium
  • brave
  • probably all other browsers on chrome base as well

After step 5, try tapping the password field on page again. Does it fill it then?

Second attempt always works. It seems, that on first autofill, the website name is not detected, but only the browser's app id. (It seems to be the same for both autofill service in notifications and autofill service in app itself.

Can provide a screencast, if that helps. But I suppose, this is easily reproducible.

I am on OnePlus 5, latest Android (9.x)

@mindrunner commented on GitHub (Oct 20, 2019): Can confirm this, however in step 4, I always observe that I do not autofill for "sitename.com", but for "com.google.chrome". Or any other appid, depending on the chrome-version I am using. This happens with - chrome - chromium - brave - probably all other browsers on chrome base as well > After step 5, try tapping the password field on page again. Does it fill it then? Second attempt always works. It seems, that on first autofill, the website name is not detected, but only the browser's app id. (It seems to be the same for both autofill service in notifications and autofill service in app itself. Can provide a screencast, if that helps. But I suppose, this is easily reproducible. I am on OnePlus 5, latest Android (9.x)
GiteaMirror commented 2025-11-26 22:29:11 -06:00
Author
Owner
Copy Link

@mpbw2 commented on GitHub (Mar 3, 2020):

@scotsman42 Is this still happening for you with the latest beta? The accessibility service was completely rewritten.

@mpbw2 commented on GitHub (Mar 3, 2020): @scotsman42 Is this still happening for you with the latest beta? The accessibility service was completely rewritten.
GiteaMirror commented 2025-11-26 22:29:12 -06:00
Author
Owner
Copy Link

@mindrunner commented on GitHub (Mar 9, 2020):

On my side that looks way better now. Haven't experienced that for a while now. Imho, this can be closed. I will come back here if it happens again.

@mindrunner commented on GitHub (Mar 9, 2020): On my side that looks way better now. Haven't experienced that for a while now. Imho, this can be closed. I will come back here if it happens again.
GiteaMirror commented 2025-11-26 22:29:12 -06:00
Author
Owner
Copy Link

@mpbw2 commented on GitHub (Mar 9, 2020):

Great, glad to hear it!

@mpbw2 commented on GitHub (Mar 9, 2020): Great, glad to hear it!
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#784
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?