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

[GH-ISSUE #598] Two Page sign in not working #6850

New Issue
Closed
opened 2026-04-10 23:12:27 -05:00 by GiteaMirror · 9 comments
GiteaMirror commented 2026-04-10 23:12:27 -05:00
Owner
Copy Link

Originally created by @VijayGawade on GitHub (Sep 10, 2019).
Original GitHub issue: https://github.com/bitwarden/android/issues/598

when we try to login in amazon.in, it will first asked for username(mail) then after click next it will asked for password.In this case bitwarden not prompt for auto filling. This app prompt after focusing on password page(2-page).Issuse is at 1st page we need to manually type usrname.

I have changed some setting in app:
Setting->Option :
change to "persist Notification"

after this auto-fill notification prompt was there ,but after selecting it is unable to set username as shoen in below screenshot.

Screenshot_20190910-102604
Screenshot_20190910-102615

try to fixed for 2 page login.

Originally created by @VijayGawade on GitHub (Sep 10, 2019). Original GitHub issue: https://github.com/bitwarden/android/issues/598 when we try to login in amazon.in, it will first asked for username(mail) then after click next it will asked for password.In this case bitwarden not prompt for auto filling. This app prompt after focusing on password page(2-page).Issuse is at 1st page we need to manually type usrname. I have changed some setting in app: Setting->Option : change to "persist Notification" after this auto-fill notification prompt was there ,but after selecting it is unable to set username as shoen in below screenshot. ![Screenshot_20190910-102604](https://user-images.githubusercontent.com/49547658/64585274-bf16e200-d3b5-11e9-8c21-05abeb2bcbf6.jpg) ![Screenshot_20190910-102615](https://user-images.githubusercontent.com/49547658/64585275-bf16e200-d3b5-11e9-87f5-fabfc91d7c1e.jpg) try to fixed for 2 page login.
GiteaMirror commented 2026-04-10 23:12:28 -05:00
Author
Owner
Copy Link

@kspearrin commented on GitHub (Sep 11, 2019):

Autofilling usernames only will not be possible on Android. I don't have any way of detecting a username field if it is not accompanied by a password field.

<!-- gh-comment-id:530351660 --> @kspearrin commented on GitHub (Sep 11, 2019): Autofilling usernames only will not be possible on Android. I don't have any way of detecting a username field if it is not accompanied by a password field.
GiteaMirror commented 2026-04-10 23:12:29 -05:00
Author
Owner
Copy Link

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

What is the difference between a username field and a password field from the perspective of an auto-fill service?

<!-- gh-comment-id:544257991 --> @mindrunner commented on GitHub (Oct 20, 2019): What is the difference between a `username` field and a `password` field from the perspective of an auto-fill service?
GiteaMirror commented 2026-04-10 23:12:30 -05:00
Author
Owner
Copy Link

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

@mindrunner A password field can be detected because there is a type that labels it as such. Based on this, we assume that the username field is a text field just before the password field. If a password field is not present, I cannot make that assumption and the username field becomes indistinguishable.

<!-- gh-comment-id:544303588 --> @kspearrin commented on GitHub (Oct 20, 2019): @mindrunner A password field can be detected because there is a type that labels it as such. Based on this, we assume that the username field is a text field just before the password field. If a password field is not present, I cannot make that assumption and the username field becomes indistinguishable.
GiteaMirror commented 2026-04-10 23:12:30 -05:00
Author
Owner
Copy Link

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

Often websites id their fields with user username pass password, and maybe some others. I think with that, you would be able to detect 80% of the pages. Since you also fill custom fields on websites, I assumed, that the heuristic in bitwarden is more than only relying on the type of the field, but also identifying fields by their id.

<!-- gh-comment-id:544304733 --> @mindrunner commented on GitHub (Oct 20, 2019): Often websites `id` their fields with `user` `username` `pass` `password`, and maybe some others. I think with that, you would be able to detect 80% of the pages. Since you also fill `custom fields` on websites, I assumed, that the heuristic in bitwarden is more than only relying on the type of the field, but also identifying fields by their `id`.
GiteaMirror commented 2026-04-10 23:12:31 -05:00
Author
Owner
Copy Link

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

@mindrunner We do not have access to that data with accessibility services. This is also why custom fields are not supported with accessibility autofill.

<!-- gh-comment-id:544304888 --> @kspearrin commented on GitHub (Oct 20, 2019): @mindrunner We do not have access to that data with accessibility services. This is also why custom fields are not supported with accessibility autofill.
GiteaMirror commented 2026-04-10 23:12:32 -05:00
Author
Owner
Copy Link

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

Ah, now I got it. :) thanks for elaboration.

<!-- gh-comment-id:544583339 --> @mindrunner commented on GitHub (Oct 21, 2019): Ah, now I got it. :) thanks for elaboration.
GiteaMirror commented 2026-04-10 23:12:33 -05:00
Author
Owner
Copy Link

@tweekmonster commented on GitHub (Oct 24, 2019):

@kspearrin I did what @VijayGawade did and enabled the persistent notification. But, when I selected my account to fill in the username field, it was my password that got filled in. Going by what you said above, I'm assuming that the username is filled, but the password overwrites it since it's being forced to fill the fields? Couldn't this be resolved by simply not allowing passwords to go into non-password fields or at least not attempt to fill two fields when there's only one present?

It would be nice to have an option to have the autofill dropdown on any field that could reasonably be a login form. What I would think is reasonable assumptions:

  • The obvious input + password fields
  • A lone non-password input
    • If you can distinguish that it's an email field, that should be a strong enough indication that this is a multi-page login
  • A lone password input

In any case, if Bitwarden can't determine if a field is fillable, couldn't the user be given the option to make that final decision?

<!-- gh-comment-id:545719787 --> @tweekmonster commented on GitHub (Oct 24, 2019): @kspearrin I did what @VijayGawade did and enabled the persistent notification. But, when I selected my account to fill in the username field, it was my password that got filled in. Going by what you said above, I'm assuming that the username is filled, but the password overwrites it since it's being forced to fill the fields? Couldn't this be resolved by simply not allowing passwords to go into non-password fields or at least not attempt to fill two fields when there's only one present? It would be nice to have an option to have the autofill dropdown on any field that could reasonably be a login form. What I would think is reasonable assumptions: - The obvious input + password fields - A lone non-password input - If you can distinguish that it's an `email` field, that should be a strong enough indication that this is a multi-page login - A lone password input In any case, if Bitwarden can't determine if a field is fillable, couldn't the user be given the option to make that final decision?
GiteaMirror commented 2026-04-10 23:12:34 -05:00
Author
Owner
Copy Link

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

I feel like it could be quite helpful if I (as a user) can choose a specific field and tell bitwarden what to fill in there. (e.g. rightclick into field -> opens menu -> bitwarden -> -> <user|password|custom>)

This could also help with other issues I have with autofill (e.g. logins with multiple fields and/or having lots of different credentials for the same page/domain)

<!-- gh-comment-id:546029871 --> @mindrunner commented on GitHub (Oct 24, 2019): I feel like it could be quite helpful if I (as a user) can choose a specific field and tell bitwarden what to fill in there. (e.g. rightclick into field -> opens menu -> bitwarden -> <entry> -> <user|password|custom>) This could also help with other issues I have with autofill (e.g. logins with multiple fields and/or having lots of different credentials for the same page/domain)
GiteaMirror commented 2026-04-10 23:12:36 -05:00
Author
Owner
Copy Link

@eliykat commented on GitHub (Apr 29, 2021):

Thanks for reporting this issue. Autofill problems can affect different sites, apps, or devices, and we’re working on improving this feature. To help us track and analyze affected sites, please lodge a report using the Google Form mentioned in this issue: #1389. Please also direct any discussion or questions to that issue. This issue will now be closed.

<!-- gh-comment-id:829701474 --> @eliykat commented on GitHub (Apr 29, 2021): Thanks for reporting this issue. Autofill problems can affect different sites, apps, or devices, and we’re working on improving this feature. To help us track and analyze affected sites, please lodge a report using the Google Form mentioned in this issue: #1389. Please also direct any discussion or questions to that issue. This issue will now be closed.
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#6850
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?