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

Autofill prompt blocks OK button for BankID, Android #1422

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

Originally created by @plumber-craic on GitHub (Feb 28, 2022).

Steps To Reproduce

Using Android 11, and BankID, (electronic identification system in Norway with over 4m users)

  1. Unlock the phone
  2. Initiate a BankID authentication session either on the phone or from a different device
  3. The BankID prompt appears on the phone, providing a unique phrase
  4. The next BankID screen requests a pin number
  5. User enters their BankID PIN
  6. The Bitwarden autofill prompt blocks access to the OK button, making it untappable.

Workaround 1

  1. enable rotation in Android. In landscape the OK button can be tapped after scrolling down

Workaround 2

  1. keep the phone locked
  2. Initiate a BankID authentication session
  3. The Bitwarden autofill prompt does not appear, so the BankID OK button can be tapped in portrait mode

Expected Result

The autofill "popover" should not block the OK button from BankID

Actual Result

The autofill "popover" blocks the OK button from BankID

Screenshots or Videos

Initial BankID prompt:
2022-02-28 13_02_11-Screenshot_20220228-125553_SIM toolkit jpg ‎- Photos

During step 2 the PIN should be entered. The Bitwarden overlay is blocking the OK button in portait mode. The overlay persists even after the user types values into this input field:
2022-02-28 13_02_24-Screenshot_20220228-125609_SIM toolkit jpg ‎- Photos

Using workaround 1, device is in landscape mode so the OK button is available:
2022-02-28 13_02_02-Screenshot_20220228-125623_SIM toolkit jpg ‎- Photos

Additional Context

NB: There is another identification system called BankID in Sweden, but this is an entirely separate system from the Norwegian one which I am reporting here.

Operating System

Android

Operating System Version

11

Device

Samsung s21

Build Version

2.16.2 (4334)

Beta

  • Using a pre-release version of the application.
Originally created by @plumber-craic on GitHub (Feb 28, 2022). ### Steps To Reproduce Using Android 11, and BankID, (electronic identification system in Norway with over 4m users) 1. Unlock the phone 2. Initiate a BankID authentication session either on the phone or from a different device 3. The BankID prompt appears on the phone, providing a unique phrase 4. The next BankID screen requests a pin number 5. User enters their BankID PIN 6. The Bitwarden autofill prompt blocks access to the OK button, making it untappable. Workaround 1 1. enable rotation in Android. In landscape the OK button can be tapped after scrolling down Workaround 2 1. keep the phone locked 2. Initiate a BankID authentication session 3. The Bitwarden autofill prompt does not appear, so the BankID OK button can be tapped in portrait mode ### Expected Result The autofill "popover" should not block the OK button from BankID ### Actual Result The autofill "popover" blocks the OK button from BankID ### Screenshots or Videos Initial BankID prompt: ![2022-02-28 13_02_11-Screenshot_20220228-125553_SIM toolkit jpg ‎- Photos](https://user-images.githubusercontent.com/48294683/155980462-5ab09781-82de-4f62-8fc0-73e5c0a10239.png) During step 2 the PIN should be entered. The Bitwarden overlay is blocking the OK button in portait mode. The overlay persists even after the user types values into this input field: ![2022-02-28 13_02_24-Screenshot_20220228-125609_SIM toolkit jpg ‎- Photos](https://user-images.githubusercontent.com/48294683/155980503-cfaeae64-2bbc-40e6-8d54-ebc02f69c2d1.png) Using workaround 1, device is in landscape mode so the OK button is available: ![2022-02-28 13_02_02-Screenshot_20220228-125623_SIM toolkit jpg ‎- Photos](https://user-images.githubusercontent.com/48294683/155980561-df1384da-a404-4e7c-ba41-407f7cb69e38.png) ### Additional Context NB: There is another identification system called BankID in Sweden, but this is an entirely separate system from the Norwegian one which I am reporting here. ### Operating System Android ### Operating System Version 11 ### Device Samsung s21 ### Build Version 2.16.2 (4334) ### Beta - [ ] Using a pre-release version of the application.
GiteaMirror added the bug label 2025-11-26 22:48:39 -06:00
GiteaMirror commented 2025-11-26 22:48:40 -06:00
Author
Owner
Copy Link

@ThrashAbaddon commented on GitHub (Jul 3, 2022):

This autofill button should be floatable, so the user can move it somewhere else where it doesn't cover an important part of the screen.

@ThrashAbaddon commented on GitHub (Jul 3, 2022): This autofill button should be floatable, so the user can move it somewhere else where it doesn't cover an important part of the screen.
GiteaMirror commented 2025-11-26 22:48:40 -06:00
Author
Owner
Copy Link

@revolutionaryking7 commented on GitHub (Jul 22, 2022):

Or this could be shown on the bottom part like enpass

@revolutionaryking7 commented on GitHub (Jul 22, 2022): Or this could be shown on the bottom part like enpass
GiteaMirror commented 2025-11-26 22:48:40 -06:00
Author
Owner
Copy Link

@kentskoglund commented on GitHub (Dec 20, 2022):

This was really annoying. I doubt there is going to be a fix for this, seeing as the problem has been reported almost 3 years ago (se Estonian Mobile-ID issue linked above). The workaround posted there seems to work for the Norwegian BankId as well. Just remember to add a comma after the URI blacklist:
Adding "androidapp://com.android.stk," URI to the blacklist did the trick.

@kentskoglund commented on GitHub (Dec 20, 2022): This was really annoying. I doubt there is going to be a fix for this, seeing as the problem has been reported almost 3 years ago (se Estonian Mobile-ID issue linked above). The workaround posted there seems to work for the Norwegian BankId as well. Just remember to add a comma after the URI blacklist: _Adding "androidapp://com.android.stk," URI to the blacklist did the trick._
GiteaMirror commented 2025-11-26 22:48:41 -06:00
Author
Owner
Copy Link

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

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

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