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

Autofill not woring on Android Binance mobile app #1093

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

Originally created by @laurentfrenette on GitHub (Sep 1, 2020).

Describe the Bug

Autofill is not working well with the mobile Binance (#1 bitcoin Exchange) app. On the login screen, the autofill pop up is there, but when you click on it, nothing happens the first time. The second time you do it, only the password gets autofilled and not the username.

Steps To Reproduce

  1. Download the official Binance app on Google Play Store https://play.google.com/store/apps/details?id=com.binance.dev&hl=fr_CA
  2. Create a dummy account entry on Bitwarden containing a regex rule for the matching keyword "Binance" and add a random email/password (no need to have a real account)
  3. Open the binance App and try to autofill the login form with the previously created dummy account. You'll notice that on the first attempt, both the email & password input won't be autofilled.
  4. Try to autofill again. This time, only the password input will be autofilled.

Expected Result

It would be expected that both the email & password input field would be autofilled when you click autofilled.

Actual Result

On the mobile Android Binance app, When you click "Autofill" the first time time, nothing happens. The second time you click it, only the password field gets autofilled and the email/username remains unfilled.

Screenshots or Videos

No screenshots available as the Binance app doesn't allow you to take screenshot for security purposes.

Environment

  • Device: Google Pixel 3
  • Operating system: Android 10
  • Build Version : QQ1A.191205.008
  • Is this a Beta release? No

Additional Context

Originally created by @laurentfrenette on GitHub (Sep 1, 2020). ## Describe the Bug Autofill is not working well with the mobile Binance (#1 bitcoin Exchange) app. On the login screen, the autofill pop up is there, but when you click on it, nothing happens the first time. The second time you do it, only the password gets autofilled and not the username. ## Steps To Reproduce 1. Download the official Binance app on Google Play Store https://play.google.com/store/apps/details?id=com.binance.dev&hl=fr_CA 2. Create a dummy account entry on Bitwarden containing a regex rule for the matching keyword "Binance" and add a random email/password (no need to have a real account) 3. Open the binance App and try to autofill the login form with the previously created dummy account. You'll notice that on the first attempt, both the email & password input won't be autofilled. 4. Try to autofill again. This time, only the password input will be autofilled. ## Expected Result It would be expected that both the email & password input field would be autofilled when you click autofilled. ## Actual Result On the mobile Android Binance app, When you click "Autofill" the first time time, nothing happens. The second time you click it, only the password field gets autofilled and the email/username remains unfilled. <!-- Comment: --> ## Screenshots or Videos No screenshots available as the Binance app doesn't allow you to take screenshot for security purposes. ## Environment - Device: Google Pixel 3 - Operating system: Android 10 - Build Version : QQ1A.191205.008 - Is this a Beta release? No ## Additional Context
GiteaMirror commented 2025-11-26 22:38:54 -06:00
Author
Owner
Copy Link

@clayadams5226 commented on GitHub (Dec 31, 2020):

Thank you for getting in touch and bringing this to our attention! We'd like to assist you further. We ask that you please contact us using our contact page, here: https://bitwarden.com/contact. You can include a link to this issue in the message content. The issue here will be closed and moved over to our Help Desk.

@clayadams5226 commented on GitHub (Dec 31, 2020): Thank you for getting in touch and bringing this to our attention! We'd like to assist you further. We ask that you please contact us using our contact page, here: https://bitwarden.com/contact. You can include a link to this issue in the message content. The issue here will be closed and moved over to our Help Desk.
GiteaMirror commented 2025-11-26 22:38:54 -06:00
Author
Owner
Copy Link

@freeelectron-ro commented on GitHub (Feb 7, 2022):

Please solve it, because it is still present this bug

@freeelectron-ro commented on GitHub (Feb 7, 2022): Please solve it, because it is still present this bug
GiteaMirror commented 2025-11-26 22:38:54 -06:00
Author
Owner
Copy Link

@RaveGun commented on GitHub (Feb 9, 2022):

Yes, I can also confirm this issue on Android 12.

@RaveGun commented on GitHub (Feb 9, 2022): Yes, I can also confirm this issue on Android 12.
GiteaMirror commented 2025-11-26 22:38:54 -06:00
Author
Owner
Copy Link

@Wladastic commented on GitHub (Mar 30, 2022):

Still an issue

@Wladastic commented on GitHub (Mar 30, 2022): Still an issue
GiteaMirror commented 2025-11-26 22:38:55 -06:00
Author
Owner
Copy Link

@halloulpsx commented on GitHub (Apr 18, 2022):

Still an issue - any planned fix for this?

@halloulpsx commented on GitHub (Apr 18, 2022): Still an issue - any planned fix for this?
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#1093
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?