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

[Android] unable to login on pokemon go app #984

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

Originally created by @eleith on GitHub (Apr 10, 2020).

Originally assigned to: @mpbw2 on GitHub.

when the password field first gets focus, the bitwarden overlay briefly flashes near the bottom before disappearing.

one can time it very quickly to tap the pop-up, then select the login, but the password is still never entered.

autofill in quick settings doesn't work either.

no workaround seems to exist, other than memorizing the password (the app somehow disables pasting into the form fields)

Environment

  • Device: pixel 2
  • Operating system: 10
  • Build Version: 2299
  • Is this a Beta release? Y

Additional Context

possibly related to #784 .

however I can use bitwarden to login to other apps just fine. only this app is problematic (which appears to use custom fields / opengl and not the default Android sdk).

Originally created by @eleith on GitHub (Apr 10, 2020). Originally assigned to: @mpbw2 on GitHub. when the password field first gets focus, the bitwarden overlay briefly flashes near the bottom before disappearing. one can time it very quickly to tap the pop-up, then select the login, but the password is still never entered. autofill in quick settings doesn't work either. no workaround seems to exist, other than memorizing the password (the app somehow disables pasting into the form fields) ## Environment - Device: pixel 2 - Operating system: 10 - Build Version: 2299 - Is this a Beta release? Y ## Additional Context possibly related to #784 . however I can use bitwarden to login to other apps just fine. only this app is problematic (which appears to use custom fields / opengl and not the default Android sdk).
GiteaMirror commented 2025-11-26 22:35:59 -06:00
Author
Owner
Copy Link

@mpbw2 commented on GitHub (Apr 10, 2020):

I think your theory about non-standard fields is correct. They don't even show up as editable nodes from accessibility, which may also explain the lack of system-level cut/copy/paste controls. The node position returned is also questionable (X:1056984576, Y:2030 on a Pixel 3) resulting in the overlay appearing at the bottom right then immediately removed once it's established that the keyboard is open.

If the fields were at least editable from the system's point of view, the quick settings tile would function as a workaround. However I believe the best thing would be for Niantic to implement Autofill Service support for use with password managers. Without that I don't think there's anything we can do here.

@mpbw2 commented on GitHub (Apr 10, 2020): I think your theory about non-standard fields is correct. They don't even show up as editable nodes from accessibility, which may also explain the lack of system-level cut/copy/paste controls. The node position returned is also questionable (X:1056984576, Y:2030 on a Pixel 3) resulting in the overlay appearing at the bottom right then immediately removed once it's established that the keyboard is open. If the fields were at least editable from the system's point of view, the quick settings tile would function as a workaround. However I believe the best thing would be for Niantic to implement Autofill Service support for use with password managers. Without that I don't think there's anything we can do here.
GiteaMirror commented 2025-11-26 22:35:59 -06:00
Author
Owner
Copy Link

@eleith commented on GitHub (Apr 10, 2020):

@mportune-bw why does the bitwarden auto fill dialog show up briefly when the password field does get focus (and then disappears)?

@eleith commented on GitHub (Apr 10, 2020): @mportune-bw why does the bitwarden auto fill dialog show up briefly when the password field does get focus (and then disappears)?
GiteaMirror commented 2025-11-26 22:35:59 -06:00
Author
Owner
Copy Link

@mpbw2 commented on GitHub (Apr 10, 2020):

The pressed/focused node is seen as password type to accessibility which is what kicks off the process and draws the initial overlay and begins tracking the anchor's position on screen. However due to the odd anchor coordinates returned by accessibility the overlay is drawn at the bottom/right of the screen, and our secondary tracking code sees this as being behind the keyboard so it's immediately hidden.

@mpbw2 commented on GitHub (Apr 10, 2020): The pressed/focused node is seen as `password` type to accessibility which is what kicks off the process and draws the initial overlay and begins tracking the anchor's position on screen. However due to the odd anchor coordinates returned by accessibility the overlay is drawn at the bottom/right of the screen, and our secondary tracking code sees this as being behind the keyboard so it's immediately hidden.
GiteaMirror commented 2025-11-26 22:35:59 -06:00
Author
Owner
Copy Link

@eleith commented on GitHub (Apr 10, 2020):

after some testing, i was able to get auto-fill in the quick settings to work. i just had to spam it a couple of times. most of the time, no text is filled, but eventually it gets filled in.

anyhow, thanks for looking into it. much appreciated.

@eleith commented on GitHub (Apr 10, 2020): after some testing, i was able to get auto-fill in the quick settings to work. i just had to spam it a couple of times. most of the time, no text is filled, but eventually it gets filled in. anyhow, thanks for looking into it. much appreciated.
GiteaMirror commented 2025-11-26 22:36:00 -06:00
Author
Owner
Copy Link

@mpbw2 commented on GitHub (Apr 10, 2020):

Interesting, thanks for the followup.

@mpbw2 commented on GitHub (Apr 10, 2020): Interesting, thanks for the followup.
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#984
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?