Autofill issue on Android - Session Timeout affects account info display (immediately redirects to Vault)

Case 1:
When Session Timeout is set to Immediately, on Android (Samsung Tab S9+) with Chrome login via Gboard integration with Bitwarden:

  • The system prompts for biometric unlock.
  • After unlocking, the account and password for that domain appear briefly for about one second.
  • Then Bitwarden immediately redirects to the My Vault page, preventing me from copying the username or password.
  • Returning to Chrome and repeating the process results in the same issue (immediate redirect to Vault).
  • If I change Session Timeout to 1 minute or longer, the issue does not occur.

Case 2:
With Session Timeout set to 1 minute, and after force closing Bitwarden to simulate a fresh launch:

  • On Chrome login, I select Bitwarden via Gboard.
  • After biometric unlock, the account info appears briefly for about one second, then it redirects to My Vault.
  • However, if I go back to Chrome and try the same process again, this time it stays on the account info screen as expected (no redirect to Vault).

Environment:

  • Bitwarden version: 2025.8.0 (downloaded from Play Store)
  • Device: Samsung Galaxy Tab S9+
  • Browser: Chrome
  • Keyboard: Gboard

Additional Issue:

  • When switching app language in Bitwarden from Chinese to English, after restarting the app, the interface still shows in Chinese even though the setting indicates English.
  • So if my wording doesn’t exactly match the official labels, please excuse me since I cannot verify the original English UI names.

I have a video recording of it.
https://youtube.com/shorts/efu9YMvUN_U?feature=share

I have the same issue, but it doesn’t happen every time and changing Session Timeout settings has no effect.

It happens to me every time and changing the session time settings also has no effect.

What has solved the issue was disabling the accessibility feature. I hope this issue is fixed soon, I rely on accessibility feature a lot.

The team is aware and working on a fix, thanks all!

1 Like