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

Auto-fill service not working on Android 9 - fill request timed out #785

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

Originally created by @lgp171188 on GitHub (Jun 22, 2019).

I have installed the 2.0.6 version of the Bitwarden app through the F-Droid repository on my Redmi Note 4 phone running Android 9. I have enabled the Auto-fill service since it works on devices running on Android 8.0 or higher and not enabled the Accessibility service'. When I click on a text input in an app, press and hold and select Auto-fill` nothing happens.

When I checked the logcat output when this happened, I see a couple of warning messages related to this issue

W RemoteFillService: PendingFillRequest timed out
W RemoteFillService: PendingFillRequest timed out after 5000 ms

I also have Keepass2Android app installed and when it is set as the app for the Auto-fill service, doing the same does show a prompt to auto-fill using it. So this looks like an issue with the Bitwarden app.

With the Accessibility service enabled, things work better and I get a notification prompting for the auto-fill most of the times, but I do not want to use it since the Auto-fill service is supposed to work and Google is deprecating the usage of Accessibility service. Also enabling it disables the boot time security which prompts for the PIN to boot the phone.

Originally created by @lgp171188 on GitHub (Jun 22, 2019). I have installed the 2.0.6 version of the Bitwarden app through the F-Droid repository on my Redmi Note 4 phone running Android 9. I have enabled the `Auto-fill service` since it works on devices running on Android 8.0 or higher and not enabled the `Accessibility service'. When I click on a text input in an app, press and hold and select `Auto-fill` nothing happens. When I checked the logcat output when this happened, I see a couple of warning messages related to this issue ``` W RemoteFillService: PendingFillRequest timed out W RemoteFillService: PendingFillRequest timed out after 5000 ms ``` I also have Keepass2Android app installed and when it is set as the app for the `Auto-fill service`, doing the same does show a prompt to auto-fill using it. So this looks like an issue with the Bitwarden app. With the `Accessibility service` enabled, things work better and I get a notification prompting for the auto-fill most of the times, but I do not want to use it since the `Auto-fill` service is supposed to work and Google is deprecating the usage of `Accessibility service`. Also enabling it disables the boot time security which prompts for the PIN to boot the phone.
GiteaMirror commented 2025-11-26 22:29:13 -06:00
Author
Owner
Copy Link

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

Does this happen in any app or only certain ones?

@kspearrin commented on GitHub (Jun 22, 2019): Does this happen in any app or only certain ones?
GiteaMirror commented 2025-11-26 22:29:14 -06:00
Author
Owner
Copy Link

@lgp171188 commented on GitHub (Jun 24, 2019):

@kspearrin, I checked only in one app before reporting this issue. I will check in other apps and post an update.

@lgp171188 commented on GitHub (Jun 24, 2019): @kspearrin, I checked only in one app before reporting this issue. I will check in other apps and post an update.
GiteaMirror commented 2025-11-26 22:29:14 -06:00
Author
Owner
Copy Link

@lgp171188 commented on GitHub (Jul 12, 2019):

@kspearrin, the auto-fill seems to work in some apps and doesn't work in a few others. Is there any additional information that I can provide in order to help diagnose this?

@lgp171188 commented on GitHub (Jul 12, 2019): @kspearrin, the auto-fill seems to work in some apps and doesn't work in a few others. Is there any additional information that I can provide in order to help diagnose this?
GiteaMirror commented 2025-11-26 22:29:14 -06:00
Author
Owner
Copy Link

@vvolkgang commented on GitHub (Jun 20, 2024):

Issue migrated to https://github.com/bitwarden/mobile/issues/545

@vvolkgang commented on GitHub (Jun 20, 2024): Issue migrated to https://github.com/bitwarden/mobile/issues/545
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#785
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?