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

Auto-fill doesn't work for sites added to home screen through Chrome #50

New Issue
Closed
opened 2025-11-07 08:24:40 -06:00 by GiteaMirror · 1 comment
GiteaMirror commented 2025-11-07 08:24:40 -06:00
Owner
Copy Link

Originally created by @c24w on GitHub (Apr 28, 2017).

When launching a full screen site, which has been added to the home screen, bitwarden doesn't recognise the site. Clicking the auto-fill notification launches bitwarden showing "Logins for android.chrome". Proceeding to add a login pre-poppulates:

Name: android.chrome
URI: androidapp://com.android.chrome

Originally created by @c24w on GitHub (Apr 28, 2017). When launching a full screen site, which has been added to the home screen, bitwarden doesn't recognise the site. Clicking the auto-fill notification launches bitwarden showing "Logins for android.chrome". Proceeding to add a login pre-poppulates: Name: android.chrome URI: androidapp://com.android.chrome
GiteaMirror commented 2025-11-07 08:24:41 -06:00
Author
Owner
Copy Link

@kspearrin commented on GitHub (Apr 28, 2017):

Unfortunately I don't see a way to make this work with the current autofill accessibility service implementation. The service currently looks for a URL bar in the browser to figure out the website address. A webview launched from he home screen likely doesn't have this. We may have to wait for Android O autofill (https://github.com/bitwarden/mobile/issues/57) to resolve this one.

@kspearrin commented on GitHub (Apr 28, 2017): Unfortunately I don't see a way to make this work with the current autofill accessibility service implementation. The service currently looks for a URL bar in the browser to figure out the website address. A webview launched from he home screen likely doesn't have this. We may have to wait for Android O autofill (https://github.com/bitwarden/mobile/issues/57) to resolve this one.
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#50
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?