Bitwarden autofill causes invisible keyboard on (most) apps that use a custom keyboard extension

[bittles]

Steps To Reproduce

1. Go to most apps that use a keyboard addon (Vivaldi and Chrome, but not Orion). These apps use a keyboard extension that replace the bar above the keyboard where Done typically appears. Vivaldi has buttons for passwords, payment options, and addresses. Chrome has buttons for passwords, payment options, and addresses with an app-specific button showing the keyboard minimizing instead of the Done button. Orion has a button for passwords.
2. Navigate to a password field. This is why its easiest to test in a browser app. Go to google.com and sign in. Or chase.com and sign in. Any website with a login will work.
3. Using either Bitwarden's autofill where it detects you have a login for the website, or just the Passwords button appears to bring up Bitwarden's overlay, if autofill is detected to be used click it so it attempts to fill in the fields. If the overlay pops up either can click a Bitwarden entry to attempt to fill in the fields or hit cancel.

Expected Result

Normal expected behavior is to return focus to the field you autofillled or had the overlay autofill and the keyboard returns.

Actual Result

Actual behavior is focus is returned to autofilled fields and keyboard doesn't appear to return, but if you click anywhere the keyboard letters would be, you will enter a key into the field. The keyboard is in fact there but is invisibile until the fields loses focus and the keyboard would minimize.

Screenshots or Videos

No response

Additional Context

Bitwarden session needs to either not be timed out or have Session Timeout set to never.

At first, for me, the keyboard would remain up and invisible and I could type and backspace from where the keys were from memory and the keyboard would stay invisible no matter how many keystrokes were sent. Deleted Bitwarden and data, reinstalled and set it up from scratch with autofill and browser extension. Now, the keyboard will remain invisible until the first keystroke and then reappear.

The key ingredient seems to be the app uses a custom bar where the default done bar above the keyboard usually is. Exception to this being Orion. This does not happen in apps without a custom bar there, or if using the Passwords app to manage passwords. The fact multiple apps can call this conflicting method indicates a problem in the implementation on the Bitwarden app side.

Assuming this is a problem on both the Bitwarden side and the app with the custom keyboard bar, with the app using a specific method to call their extension that conflicts with a method Bitwarden uses.

This started happening sometime around Bitwarden version 2024.10.0 or 2024.11.0 as I thought it was originally a bug caused from uodating to iOS 18.1. It wasn’t until this last week I decided to see if it happened with the Passwords app instead of Bitwarden, and then tried to narrow down when Bitwarden causes this to happen.

Build Version

2025.1.3 currently but started around 2024.10.0 or 2024.11.0

What server are you connecting to?

US

Self-host Server Version

No response

Environment Details

No response

Issue Tracking Info

• I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.