github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-05-05 23:38:51 -05:00
Code Issues 1.1k Packages Projects Releases 122 Wiki Activity

[GH-ISSUE #5777] [PM-25143] 2025.8.0 autofill logins disappear #50413

New Issue
Closed
opened 2026-05-01 12:54:06 -05:00 by GiteaMirror · 44 comments
GiteaMirror commented 2026-05-01 12:54:06 -05:00
Owner
Copy Link

Originally created by @olegbilovus on GitHub (Aug 23, 2025).
Original GitHub issue: https://github.com/bitwarden/android/issues/5777

Steps To Reproduce

  1. Go to any website with a login in Bitwarden
  2. Click on the Bitwarden Icon on top of the keyboard

Expected Result

Shows the available logins and select one of those for the autofill

Actual Result

It will show the available logins for 1 second and then goes to the main activity without the possibility select a login for the autofill

Screenshots or Videos

No response

Additional Context

This bug is new in 2025.8.0. The 2025.7.2 was working fine.

In the logs, it shows there is a MainActivity destination changed: root which may be the cause of it.

Logs Bitwarden Android Log Start Time: 2025-08-23 08:25:04:309 Log Duration: 1d App Version: 2025.8.0 (20577) Build: release/standard Operating System: 15 (35) Device: samsung SM-G998B Fingerprint: samsung/p3sxeea/p3s:15/AP3A.240905.015.A2/G998BXXSFHYE1:user/release-keys 2025-08-23 08:25:04:313 – DEBUG – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.vaultunlockednavbar.VaultUnlockedNavbarRoute in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute 2025-08-23 08:25:04:360 – DEBUG – VaultUnlockedNavBarScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.settings.about.SettingsAboutRoute.Standard in com.x8bit.bitwarden.ui.platform.feature.settings.SettingsGraphRoute 2025-08-23 08:25:06:914 – DEBUG – Network status change: Wifi(strength=UNKNOWN) 2025-08-23 08:25:06:924 – DEBUG – Current environment: EU 2025-08-23 08:25:06:924 – DEBUG – Current environment: EU 2025-08-23 08:25:06:934 – DEBUG – Parsing AssistStructure -- 1092 2025-08-23 08:25:06:933 – DEBUG – Begin processing Autofill fill request -- 1092 2025-08-23 08:25:06:937 – ERROR – Autofill request isInlineEnabled=true -- 1092 2025-08-23 08:25:06:937 – DEBUG – Autofill request is Fillable -- 1092 2025-08-23 08:25:06:937 – DEBUG – Autofill request constructing FilledData 2025-08-23 08:25:06:937 – DEBUG – Autofill request constructing SaveInfo -- 1092 2025-08-23 08:25:06:937 – DEBUG – Autofill request isInCompatMode=false -- 1092 2025-08-23 08:25:06:937 – WARNING – Autofill request constructing FillResponse 2025-08-23 08:25:06:939 – DEBUG – Autofill request success: Fillable -- 1092 2025-08-23 08:25:06:939 – DEBUG – Autofill request isInlineCompatible=true 2025-08-23 08:25:07:428 – DEBUG – BitwardenNetworkClient – --> GET https://api.bitwarden.eu/config 2025-08-23 08:25:07:507 – DEBUG – App is foregrounded 2025-08-23 08:25:07:529 – DEBUG – MainActivity destination changed: root 2025-08-23 08:25:07:545 – DEBUG – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.splash.SplashRoute 2025-08-23 08:25:07:561 – DEBUG – RootNavScreen destination changed: com.x8bit.bitwarden.ui.auth.feature.vaultunlock.VaultUnlockRoute$Standard/{encodedData} 2025-08-23 08:25:07:686 – DEBUG – BitwardenNetworkClient – <-- 200 https://api.bitwarden.eu/config (257ms, unknown-length body) 2025-08-23 08:25:08:290 – DEBUG – RootNavScreen destination changed: com.x8bit.bitwarden.ui.auth.feature.vaultunlock.VaultUnlockRoute$Standard/{encodedData} 2025-08-23 08:25:08:293 – DEBUG – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.vaultunlockednavbar.VaultUnlockedNavbarRoute in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute 2025-08-23 08:25:08:293 – DEBUG – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.vaultunlockednavbar.VaultUnlockedNavbarRoute in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute 2025-08-23 08:25:08:294 – DEBUG – RootNavScreen destination changed: Wb.K/{encodedData} in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute 2025-08-23 08:25:08:295 – DEBUG – RootNavScreen destination changed: Wb.K/{encodedData} in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute 2025-08-23 08:25:08:817 – DEBUG – MainActivity destination changed: root 2025-08-23 08:25:08:829 – DEBUG – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.splash.SplashRoute 2025-08-23 08:25:08:842 – DEBUG – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.vaultunlockednavbar.VaultUnlockedNavbarRoute in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute 2025-08-23 08:25:08:873 – DEBUG – VaultUnlockedNavBarScreen destination changed: com.x8bit.bitwarden.ui.vault.feature.vault.VaultRoute in com.x8bit.bitwarden.ui.vault.feature.vault.VaultGraphRoute 2025-08-23 08:25:10:340 – DEBUG – VaultUnlockedNavBarScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.settings.SettingsRoute$Standard/{encodedData} in com.x8bit.bitwarden.ui.platform.feature.settings.SettingsGraphRoute 2025-08-23 08:25:10:342 – DEBUG – VaultUnlockedNavBarScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.settings.about.SettingsAboutRoute.Standard in com.x8bit.bitwarden.ui.platform.feature.settings.SettingsGraphRoute

Build Version

2025.8.0

What server are you connecting to?

EU

Self-host Server Version

No response

Environment Details

© Bitwarden Inc. 2015-2025

Version: 2025.8.0 (20577)
📱 samsung SM-G998B 🤖 15@35 📦 prod
🧱 commit: bitwarden/android/release/2025.8-rc32@1c525b9dfc588105e1fd8f3ad2d4196803c19cd7
💻 build source: bitwarden/android/actions/runs/16834718954/attempts/1
🦀 SDK: 1.0.0-2450-9fe3aeda
🌩 Server: 2025.8.0 @ EU

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.
Originally created by @olegbilovus on GitHub (Aug 23, 2025). Original GitHub issue: https://github.com/bitwarden/android/issues/5777 ### Steps To Reproduce 1. Go to any website with a login in Bitwarden 2. Click on the Bitwarden Icon on top of the keyboard ### Expected Result Shows the available logins and select one of those for the autofill ### Actual Result It will show the available logins for 1 second and then goes to the main activity without the possibility select a login for the autofill ### Screenshots or Videos _No response_ ### Additional Context This bug is new in 2025.8.0. The 2025.7.2 was working fine. In the logs, it shows there is a `MainActivity destination changed: root` which may be the cause of it. <details><summary>Logs</summary> <code> Bitwarden Android Log Start Time: 2025-08-23 08:25:04:309 Log Duration: 1d App Version: 2025.8.0 (20577) Build: release/standard Operating System: 15 (35) Device: samsung SM-G998B Fingerprint: samsung/p3sxeea/p3s:15/AP3A.240905.015.A2/G998BXXSFHYE1:user/release-keys 2025-08-23 08:25:04:313 – DEBUG – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.vaultunlockednavbar.VaultUnlockedNavbarRoute in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute 2025-08-23 08:25:04:360 – DEBUG – VaultUnlockedNavBarScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.settings.about.SettingsAboutRoute.Standard in com.x8bit.bitwarden.ui.platform.feature.settings.SettingsGraphRoute 2025-08-23 08:25:06:914 – DEBUG – Network status change: Wifi(strength=UNKNOWN) 2025-08-23 08:25:06:924 – DEBUG – Current environment: EU 2025-08-23 08:25:06:924 – DEBUG – Current environment: EU 2025-08-23 08:25:06:934 – DEBUG – Parsing AssistStructure -- 1092 2025-08-23 08:25:06:933 – DEBUG – Begin processing Autofill fill request -- 1092 2025-08-23 08:25:06:937 – ERROR – Autofill request isInlineEnabled=true -- 1092 2025-08-23 08:25:06:937 – DEBUG – Autofill request is Fillable -- 1092 2025-08-23 08:25:06:937 – DEBUG – Autofill request constructing FilledData 2025-08-23 08:25:06:937 – DEBUG – Autofill request constructing SaveInfo -- 1092 2025-08-23 08:25:06:937 – DEBUG – Autofill request isInCompatMode=false -- 1092 2025-08-23 08:25:06:937 – WARNING – Autofill request constructing FillResponse 2025-08-23 08:25:06:939 – DEBUG – Autofill request success: Fillable -- 1092 2025-08-23 08:25:06:939 – DEBUG – Autofill request isInlineCompatible=true 2025-08-23 08:25:07:428 – DEBUG – BitwardenNetworkClient – --> GET https://api.bitwarden.eu/config 2025-08-23 08:25:07:507 – DEBUG – App is foregrounded 2025-08-23 08:25:07:529 – DEBUG – MainActivity destination changed: root 2025-08-23 08:25:07:545 – DEBUG – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.splash.SplashRoute 2025-08-23 08:25:07:561 – DEBUG – RootNavScreen destination changed: com.x8bit.bitwarden.ui.auth.feature.vaultunlock.VaultUnlockRoute$Standard/{encodedData} 2025-08-23 08:25:07:686 – DEBUG – BitwardenNetworkClient – <-- 200 https://api.bitwarden.eu/config (257ms, unknown-length body) 2025-08-23 08:25:08:290 – DEBUG – RootNavScreen destination changed: com.x8bit.bitwarden.ui.auth.feature.vaultunlock.VaultUnlockRoute$Standard/{encodedData} 2025-08-23 08:25:08:293 – DEBUG – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.vaultunlockednavbar.VaultUnlockedNavbarRoute in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute 2025-08-23 08:25:08:293 – DEBUG – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.vaultunlockednavbar.VaultUnlockedNavbarRoute in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute 2025-08-23 08:25:08:294 – DEBUG – RootNavScreen destination changed: Wb.K/{encodedData} in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute 2025-08-23 08:25:08:295 – DEBUG – RootNavScreen destination changed: Wb.K/{encodedData} in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute 2025-08-23 08:25:08:817 – DEBUG – MainActivity destination changed: root 2025-08-23 08:25:08:829 – DEBUG – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.splash.SplashRoute 2025-08-23 08:25:08:842 – DEBUG – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.vaultunlockednavbar.VaultUnlockedNavbarRoute in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute 2025-08-23 08:25:08:873 – DEBUG – VaultUnlockedNavBarScreen destination changed: com.x8bit.bitwarden.ui.vault.feature.vault.VaultRoute in com.x8bit.bitwarden.ui.vault.feature.vault.VaultGraphRoute 2025-08-23 08:25:10:340 – DEBUG – VaultUnlockedNavBarScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.settings.SettingsRoute$Standard/{encodedData} in com.x8bit.bitwarden.ui.platform.feature.settings.SettingsGraphRoute 2025-08-23 08:25:10:342 – DEBUG – VaultUnlockedNavBarScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.settings.about.SettingsAboutRoute.Standard in com.x8bit.bitwarden.ui.platform.feature.settings.SettingsGraphRoute </code> </details> ### Build Version 2025.8.0 ### What server are you connecting to? EU ### Self-host Server Version _No response_ ### Environment Details © Bitwarden Inc. 2015-2025 Version: 2025.8.0 (20577) 📱 samsung SM-G998B 🤖 15@35 📦 prod 🧱 commit: bitwarden/android/release/2025.8-rc32@1c525b9dfc588105e1fd8f3ad2d4196803c19cd7 💻 build source: bitwarden/android/actions/runs/16834718954/attempts/1 🦀 SDK: 1.0.0-2450-9fe3aeda 🌩 Server: 2025.8.0 @ EU ### Issue Tracking Info - [x] 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.
GiteaMirror added the bugapp:password-manager labels 2026-05-01 12:54:06 -05:00
GiteaMirror commented 2026-05-01 12:54:09 -05:00
Author
Owner
Copy Link

@bitwarden-bot commented on GitHub (Aug 23, 2025):

Thank you for your report! We've added this to our internal board for review.
ID: PM-25143

<!-- gh-comment-id:3216459579 --> @bitwarden-bot commented on GitHub (Aug 23, 2025): Thank you for your report! We've added this to our internal board for review. ID: PM-25143
GiteaMirror commented 2026-05-01 12:54:10 -05:00
Author
Owner
Copy Link

@kaurav99 commented on GitHub (Aug 24, 2025):

I am also facing the same issue since I updated the app to the latest verion 2025.8.0.

<!-- gh-comment-id:3218237073 --> @kaurav99 commented on GitHub (Aug 24, 2025): I am also facing the same issue since I updated the app to the latest verion 2025.8.0.
GiteaMirror commented 2026-05-01 12:54:12 -05:00
Author
Owner
Copy Link

@The-Engineer commented on GitHub (Aug 24, 2025):

Same here on Samsung A54 and Samsung Tab S9 FE+ since the 2025.8.0 update. Both have the latest Android 15 and OneUI 7.0 without root or other mods

<!-- gh-comment-id:3218335226 --> @The-Engineer commented on GitHub (Aug 24, 2025): Same here on Samsung A54 and Samsung Tab S9 FE+ since the 2025.8.0 update. Both have the latest Android 15 and OneUI 7.0 without root or other mods
GiteaMirror commented 2026-05-01 12:54:14 -05:00
Author
Owner
Copy Link

@rmcdowell-bitwarden commented on GitHub (Aug 25, 2025):

Hi there,

I am unable to reproduce this issue, it has been escalated for further investigation. If you have more information that can help us, please add it below.

Thanks!

<!-- gh-comment-id:3218763427 --> @rmcdowell-bitwarden commented on GitHub (Aug 25, 2025): Hi there, I am unable to reproduce this issue, it has been escalated for further investigation. If you have more information that can help us, please add it below. Thanks!
GiteaMirror commented 2026-05-01 12:54:16 -05:00
Author
Owner
Copy Link

@ghost commented on GitHub (Aug 25, 2025):

Probably not what you mean with "more information", but anyway: I have the issue on a Xiaomi Device (HyperOS). But not on a Google Device (GrapheneOS).

<!-- gh-comment-id:3218795776 --> @ghost commented on GitHub (Aug 25, 2025): Probably not what you mean with "more information", but anyway: I have the issue on a Xiaomi Device (HyperOS). But not on a Google Device (GrapheneOS).
GiteaMirror commented 2026-05-01 12:54:18 -05:00
Author
Owner
Copy Link

@o2rhkzqx commented on GitHub (Aug 25, 2025):

Hi there,

I am unable to reproduce this issue, it has been escalated for further investigation. If you have more information that can help us, please add it below.

Thanks!

Attaching video for your reference with device and Bitwarden details:
© Bitwarden Inc. 2015-2025
Version: 2025.8.0 (20577)
📱 samsung SM-S928B 🤖 15@35 📦 prod -fdroid
🧱 commit: bitwarden/android/release/2025.8-rc32@1c525b9dfc588105e1fd8f3ad2d4196803c19cd7
💻 build source: bitwarden/android/actions/runs/16834718954/attempts/1
🦀 SDK: 1.0.0-2450-9fe3aeda
🌩 Server: 2025.8.0 @ US

https://github.com/user-attachments/assets/fae5daf5-b9df-414e-996a-a362640025ec

<!-- gh-comment-id:3218899821 --> @o2rhkzqx commented on GitHub (Aug 25, 2025): > Hi there, > > I am unable to reproduce this issue, it has been escalated for further investigation. If you have more information that can help us, please add it below. > > Thanks! Attaching video for your reference with device and Bitwarden details: © Bitwarden Inc. 2015-2025 Version: 2025.8.0 (20577) 📱 samsung SM-S928B 🤖 15@35 📦 prod -fdroid 🧱 commit: bitwarden/android/release/2025.8-rc32@1c525b9dfc588105e1fd8f3ad2d4196803c19cd7 💻 build source: bitwarden/android/actions/runs/16834718954/attempts/1 🦀 SDK: 1.0.0-2450-9fe3aeda 🌩 Server: 2025.8.0 @ US https://github.com/user-attachments/assets/fae5daf5-b9df-414e-996a-a362640025ec
GiteaMirror commented 2026-05-01 12:54:20 -05:00
Author
Owner
Copy Link

@o2rhkzqx commented on GitHub (Aug 25, 2025):

Hi all,
Temporary workaround for this issue is increase session timeout so it will stay unlocked for chosen amount of time and will work as usual.

<!-- gh-comment-id:3218908003 --> @o2rhkzqx commented on GitHub (Aug 25, 2025): Hi all, Temporary workaround for this issue is increase session timeout so it will stay unlocked for chosen amount of time and will work as usual.
GiteaMirror commented 2026-05-01 12:54:22 -05:00
Author
Owner
Copy Link

@olegbilovus commented on GitHub (Aug 25, 2025):

Hi all,
Temporary workaround for this issue is increase session timeout so it will stay unlocked for chosen amount of time and will work as usual.

I just tried it and the timeout must be >= 15 minutes. If you select 1 or 5 minutes, the bug will still be there.

<!-- gh-comment-id:3218915239 --> @olegbilovus commented on GitHub (Aug 25, 2025): > Hi all, > Temporary workaround for this issue is increase session timeout so it will stay unlocked for chosen amount of time and will work as usual. I just tried it and the timeout must be >= 15 minutes. If you select 1 or 5 minutes, the bug will still be there.
GiteaMirror commented 2026-05-01 12:54:24 -05:00
Author
Owner
Copy Link

@o2rhkzqx commented on GitHub (Aug 25, 2025):

Hi all,
Temporary workaround for this issue is increase session timeout so it will stay unlocked for chosen amount of time and will work as usual.

I just tried it and the timeout must be >= 15 minutes. If you select 1 or 5 minutes, the bug will still be there.

It's working even with 1 and 5 options too in my device.

<!-- gh-comment-id:3218922187 --> @o2rhkzqx commented on GitHub (Aug 25, 2025): > > Hi all, > > Temporary workaround for this issue is increase session timeout so it will stay unlocked for chosen amount of time and will work as usual. > > I just tried it and the timeout must be >= 15 minutes. If you select 1 or 5 minutes, the bug will still be there. It's working even with 1 and 5 options too in my device.
GiteaMirror commented 2026-05-01 12:54:27 -05:00
Author
Owner
Copy Link

@olegbilovus commented on GitHub (Aug 25, 2025):

Hi all,
Temporary workaround for this issue is increase session timeout so it will stay unlocked for chosen amount of time and will work as usual.

I just tried it and the timeout must be >= 15 minutes. If you select 1 or 5 minutes, the bug will still be there.

It's working even with 1 and 5 options too in my device.

I tried again with 1 minute and if the vault is already locked, it will be bugged, but if the vault is not locked(the timeout didn't run out) it will work.

<!-- gh-comment-id:3218928504 --> @olegbilovus commented on GitHub (Aug 25, 2025): > > > Hi all, > > > Temporary workaround for this issue is increase session timeout so it will stay unlocked for chosen amount of time and will work as usual. > > > > I just tried it and the timeout must be >= 15 minutes. If you select 1 or 5 minutes, the bug will still be there. > > It's working even with 1 and 5 options too in my device. I tried again with 1 minute and if the vault is already locked, it will be bugged, but if the vault is not locked(the timeout didn't run out) it will work.
GiteaMirror commented 2026-05-01 12:54:32 -05:00
Author
Owner
Copy Link

@o2rhkzqx commented on GitHub (Aug 25, 2025):

Hi all,
Temporary workaround for this issue is increase session timeout so it will stay unlocked for chosen amount of time and will work as usual.

I just tried it and the timeout must be >= 15 minutes. If you select 1 or 5 minutes, the bug will still be there.

It's working even with 1 and 5 options too in my device.

I tried again with 1 minute and if the vault is already locked, it will be bugged, but if the vault is not locked(the timeout didn't run out) it will work.

First time you will have to unlock ut then again you click on the field then it will stay there.

<!-- gh-comment-id:3218979056 --> @o2rhkzqx commented on GitHub (Aug 25, 2025): > > > > Hi all, > > > > Temporary workaround for this issue is increase session timeout so it will stay unlocked for chosen amount of time and will work as usual. > > > > > > > > > I just tried it and the timeout must be >= 15 minutes. If you select 1 or 5 minutes, the bug will still be there. > > > > > > It's working even with 1 and 5 options too in my device. > > I tried again with 1 minute and if the vault is already locked, it will be bugged, but if the vault is not locked(the timeout didn't run out) it will work. First time you will have to unlock ut then again you click on the field then it will stay there.
GiteaMirror commented 2026-05-01 12:54:36 -05:00
Author
Owner
Copy Link

@The-Engineer commented on GitHub (Aug 25, 2025):

Same here on Samsung A54 and Samsung Tab S9 FE+ since the 2025.8.0 update. Both have the latest Android 15 and OneUI 7.0 without root or other mods

can confirm, setting the vault timeout to longer than 15mins helps solve the issue for me too

<!-- gh-comment-id:3220101621 --> @The-Engineer commented on GitHub (Aug 25, 2025): > Same here on Samsung A54 and Samsung Tab S9 FE+ since the 2025.8.0 update. Both have the latest Android 15 and OneUI 7.0 without root or other mods can confirm, setting the vault timeout to longer than 15mins helps solve the issue for me too
GiteaMirror commented 2026-05-01 12:54:39 -05:00
Author
Owner
Copy Link

@ghost commented on GitHub (Aug 25, 2025):

I switched back to an older version. This newest update is a disaster.

<!-- gh-comment-id:3220802063 --> @ghost commented on GitHub (Aug 25, 2025): I switched back to an older version. This newest update is a disaster.
GiteaMirror commented 2026-05-01 12:54:42 -05:00
Author
Owner
Copy Link

@n0k0m3 commented on GitHub (Aug 25, 2025):

Confirms downgrading to 2025.7.2 solves the issue. Also looks like this issue is unique to Samsung OneUI (S21, S25) and Xiaomi HyperOS (Poco X4 GT), works fine on Google Pixel (I own all of these devicesand was able to test on these OSes)

<!-- gh-comment-id:3221145172 --> @n0k0m3 commented on GitHub (Aug 25, 2025): Confirms downgrading to 2025.7.2 solves the issue. Also looks like this issue is unique to Samsung OneUI (S21, S25) and Xiaomi HyperOS (Poco X4 GT), works fine on Google Pixel (I own all of these devicesand was able to test on these OSes)
GiteaMirror commented 2026-05-01 12:54:47 -05:00
Author
Owner
Copy Link

@T-727 commented on GitHub (Aug 26, 2025):

Also looks like this issue is unique to Samsung OneUI (S21, S25) and Xiaomi HyperOS (Poco X4 GT)

Plus Nothing OS 3.2 (Nothing Phone 2)

<!-- gh-comment-id:3224120559 --> @T-727 commented on GitHub (Aug 26, 2025): > Also looks like this issue is unique to Samsung OneUI (S21, S25) and Xiaomi HyperOS (Poco X4 GT) Plus Nothing OS 3.2 (Nothing Phone 2)
GiteaMirror commented 2026-05-01 12:54:50 -05:00
Author
Owner
Copy Link

@davidmtml commented on GitHub (Aug 26, 2025):

Only because I haven't seen specifically the S22 mentioned, my S22+ is having the same issue.

<!-- gh-comment-id:3224737693 --> @davidmtml commented on GitHub (Aug 26, 2025): Only because I haven't seen specifically the S22 mentioned, my S22+ is having the same issue.
GiteaMirror commented 2026-05-01 12:54:51 -05:00
Author
Owner
Copy Link

@zombipuppy commented on GitHub (Aug 26, 2025):

Having this issue on my S22.

<!-- gh-comment-id:3225746376 --> @zombipuppy commented on GitHub (Aug 26, 2025): Having this issue on my S22.
GiteaMirror commented 2026-05-01 12:54:52 -05:00
Author
Owner
Copy Link

@riccardo1991 commented on GitHub (Aug 26, 2025):

Same issue on my Fairphone 5 wih Android 15

<!-- gh-comment-id:3225808288 --> @riccardo1991 commented on GitHub (Aug 26, 2025): Same issue on my Fairphone 5 wih Android 15
GiteaMirror commented 2026-05-01 12:54:52 -05:00
Author
Owner
Copy Link

@Sym8 commented on GitHub (Aug 27, 2025):

+1 same issue, OnePlus 11.

<!-- gh-comment-id:3226373040 --> @Sym8 commented on GitHub (Aug 27, 2025): +1 same issue, OnePlus 11.
GiteaMirror commented 2026-05-01 12:54:53 -05:00
Author
Owner
Copy Link

@dg1234567 commented on GitHub (Aug 27, 2025):

Came here to mention I'm having the same issue on an S25 with one ui 7 and latest update.

<!-- gh-comment-id:3226514519 --> @dg1234567 commented on GitHub (Aug 27, 2025): Came here to mention I'm having the same issue on an S25 with one ui 7 and latest update.
GiteaMirror commented 2026-05-01 12:54:54 -05:00
Author
Owner
Copy Link

@DerzelasFlo commented on GitHub (Aug 27, 2025):

I am facing the same issue on Samsung Galaxy S24+. The only solution I applied was to downgrade Bitwarden app to a previous version and stop update automatically from Google Store. Now it works ok.
However, I realise that above solution is only temporary and probably I expose myself to some threats not being updated.
Looking forward to hear from Bitwarden team that they solved the bug.

<!-- gh-comment-id:3226950470 --> @DerzelasFlo commented on GitHub (Aug 27, 2025): I am facing the same issue on Samsung Galaxy S24+. The only solution I applied was to downgrade Bitwarden app to a previous version and stop update automatically from Google Store. Now it works ok. However, I realise that above solution is only temporary and probably I expose myself to some threats not being updated. Looking forward to hear from Bitwarden team that they solved the bug.
GiteaMirror commented 2026-05-01 12:54:56 -05:00
Author
Owner
Copy Link

@GitStudying commented on GitHub (Aug 27, 2025):

Also here, Samsung S23 Ultra OneUI 7 latest version. So Samsung at least is very consistently getting this bug. Some other also but some not. Not sure then what the common cause is, either way I think any Samsung s21 and up and any variant will have this with 2025.8.0.
Please let us know if you can reproduce the issue or still need more help.

<!-- gh-comment-id:3227769224 --> @GitStudying commented on GitHub (Aug 27, 2025): Also here, Samsung S23 Ultra OneUI 7 latest version. So Samsung at least is very consistently getting this bug. Some other also but some not. Not sure then what the common cause is, either way I think any Samsung s21 and up and any variant will have this with 2025.8.0. Please let us know if you can reproduce the issue or still need more help.
GiteaMirror commented 2026-05-01 12:54:58 -05:00
Author
Owner
Copy Link

@SaintPatrck commented on GitHub (Aug 27, 2025):

Hi all,

We have identified the issue and are working on a fix. It relates to our fix for the notification bar bug present in some revisions of Android 15 (#5617). We are attempting to find a solution that does not re-introduce the system bar inconsistencies.

<!-- gh-comment-id:3228462793 --> @SaintPatrck commented on GitHub (Aug 27, 2025): Hi all, We have identified the issue and are working on a fix. It relates to our fix for the notification bar bug present in some revisions of Android 15 (#5617). We are attempting to find a solution that does not re-introduce the system bar inconsistencies.
GiteaMirror commented 2026-05-01 12:55:00 -05:00
Author
Owner
Copy Link

@PineappleXBunz commented on GitHub (Aug 28, 2025):

I'm experiencing the same issue with my S25 Edge (OneUI 7). Very very annoying...

<!-- gh-comment-id:3235027316 --> @PineappleXBunz commented on GitHub (Aug 28, 2025): I'm experiencing the same issue with my S25 Edge (OneUI 7). Very very annoying...
GiteaMirror commented 2026-05-01 12:55:00 -05:00
Author
Owner
Copy Link

@dg1234567 commented on GitHub (Aug 29, 2025):

Appreciateed > Hi all,

We have identified the issue and are working on a fix. It relates to our fix for the notification bar bug present in some revisions of Android 15 (#5617). We are attempting to find a solution that does not re-introduce the system bar inconsistencies.

<!-- gh-comment-id:3235594908 --> @dg1234567 commented on GitHub (Aug 29, 2025): Appreciateed > Hi all, > > We have identified the issue and are working on a fix. It relates to our fix for the notification bar bug present in some revisions of Android 15 (#5617). We are attempting to find a solution that does not re-introduce the system bar inconsistencies.
GiteaMirror commented 2026-05-01 12:55:02 -05:00
Author
Owner
Copy Link

@blair287 commented on GitHub (Aug 29, 2025):

Bitwarden is nothing but constant bugs how is this stuff not tested? It takes 10 seconds to find these bugs after a new release it's like amateur hour.

<!-- gh-comment-id:3238356453 --> @blair287 commented on GitHub (Aug 29, 2025): Bitwarden is nothing but constant bugs how is this stuff not tested? It takes 10 seconds to find these bugs after a new release it's like amateur hour.
GiteaMirror commented 2026-05-01 12:55:03 -05:00
Author
Owner
Copy Link

@ssuets110 commented on GitHub (Aug 30, 2025):

Phone: S25 plus
Latest version as in the subject. 2025.8.0
Issue is reproducible as reported by the author, only when bitwarden is locked, however if unlocked then no issue is observed.

<!-- gh-comment-id:3239161645 --> @ssuets110 commented on GitHub (Aug 30, 2025): Phone: S25 plus Latest version as in the subject. 2025.8.0 Issue is reproducible as reported by the author, only when bitwarden is locked, however if unlocked then no issue is observed.
GiteaMirror commented 2026-05-01 12:55:03 -05:00
Author
Owner
Copy Link

@PaidThaFossToBeDaBoss commented on GitHub (Aug 30, 2025):

This bug is also affecting my Sony Xperia 1 V, Android 15.

<!-- gh-comment-id:3239173974 --> @PaidThaFossToBeDaBoss commented on GitHub (Aug 30, 2025): This bug is also affecting my Sony Xperia 1 V, Android 15.
GiteaMirror commented 2026-05-01 12:55:04 -05:00
Author
Owner
Copy Link

@infinitytec commented on GitHub (Aug 30, 2025):

Same issue here on S25 Ultra OneUI7 as of two or so days ago.

© Bitwarden Inc. 2015-2025

Version: 2025.8.0 (20577)
📱 samsung SM-S938U1 🤖 15@35 📦 prod
🧱 commit: bitwarden/android/release/2025.8-rc32@1c525b9dfc588105e1fd8f3ad2d4196803c19cd7
💻 build source: bitwarden/android/actions/runs/16834718954/attempts/1
🦀 SDK: 1.0.0-2450-9fe3aeda
🌩 Server: 2025.8.0 @ US

<!-- gh-comment-id:3239372289 --> @infinitytec commented on GitHub (Aug 30, 2025): Same issue here on S25 Ultra OneUI7 as of two or so days ago. © Bitwarden Inc. 2015-2025 Version: 2025.8.0 (20577) 📱 samsung SM-S938U1 🤖 15@35 📦 prod 🧱 commit: bitwarden/android/release/2025.8-rc32@1c525b9dfc588105e1fd8f3ad2d4196803c19cd7 💻 build source: bitwarden/android/actions/runs/16834718954/attempts/1 🦀 SDK: 1.0.0-2450-9fe3aeda 🌩 Server: 2025.8.0 @ US
GiteaMirror commented 2026-05-01 12:55:06 -05:00
Author
Owner
Copy Link

@dg1234567 commented on GitHub (Aug 31, 2025):

This is one of the best free open source password manager apps out there with very very very few noticeable bugs. > Bitwarden is nothing but constant bugs how is this stuff not tested? It takes 10 seconds to find these bugs after a new release it's like amateur hour.

<!-- gh-comment-id:3239690275 --> @dg1234567 commented on GitHub (Aug 31, 2025): This is one of the best free open source password manager apps out there with very very very few noticeable bugs. > Bitwarden is nothing but constant bugs how is this stuff not tested? It takes 10 seconds to find these bugs after a new release it's like amateur hour.
GiteaMirror commented 2026-05-01 12:55:10 -05:00
Author
Owner
Copy Link

@n0k0m3 commented on GitHub (Aug 31, 2025):

@SaintPatrck
Can you guys give us the hotfix (2025.8.1 for example)with the commit reversed. Then deal with the inconsistency later? This is literally breaking bug and the inconsistent system bar is just cosmetic.

Hi all,

We have identified the issue and are working on a fix. It relates to our fix for the notification bar bug present in some revisions of Android 15 (#5617). We are attempting to find a solution that does not re-introduce the system bar inconsistencies.

Also to new reporters please stop reporting if you have either Samsung OneUI, NothingOS, HyperOS (Xiaomi), Fairphone, Oneplus. These phones/OSes are already reported. Reporting these will dilute the conversation.

<!-- gh-comment-id:3239716174 --> @n0k0m3 commented on GitHub (Aug 31, 2025): @SaintPatrck Can you guys give us the hotfix (2025.8.1 for example)with the commit reversed. Then deal with the inconsistency later? This is literally breaking bug and the inconsistent system bar is just cosmetic. > Hi all, > > We have identified the issue and are working on a fix. It relates to our fix for the notification bar bug present in some revisions of Android 15 ([#5617](https://github.com/bitwarden/android/pull/5617)). We are attempting to find a solution that does not re-introduce the system bar inconsistencies. Also to new reporters please stop reporting if you have either Samsung OneUI, NothingOS, HyperOS (Xiaomi), Fairphone, Oneplus. These phones/OSes are already reported. Reporting these will dilute the conversation.
GiteaMirror commented 2026-05-01 12:55:16 -05:00
Author
Owner
Copy Link

@AcidRaZor commented on GitHub (Aug 31, 2025):

Bitwarden is nothing but constant bugs how is this stuff not tested? It takes 10 seconds to find these bugs after a new release it's like amateur hour.

There are literal hundreds of different phones and implementations of Android, it not more. You expect them to have a phone of each brand, make, model, Android OS version and its variants and flavours, and run through a QA process to ensure 0 bugs when doing a release?

Especially when those same phones are also constantly updated with whatever flavour of OneUI (for example) is out there?

Please come back down to reality and join us for a second. Your comment is unnecessary and doesn't bring value to the overall conversation.

<!-- gh-comment-id:3239992340 --> @AcidRaZor commented on GitHub (Aug 31, 2025): > Bitwarden is nothing but constant bugs how is this stuff not tested? It takes 10 seconds to find these bugs after a new release it's like amateur hour. There are literal hundreds of different phones and implementations of Android, it not more. You expect them to have a phone of each brand, make, model, Android OS version and its variants and flavours, and run through a QA process to ensure 0 bugs when doing a release? Especially when those same phones are also constantly updated with whatever flavour of OneUI (for example) is out there? Please come back down to reality and join us for a second. Your comment is unnecessary and doesn't bring value to the overall conversation.
GiteaMirror commented 2026-05-01 12:55:20 -05:00
Author
Owner
Copy Link

@buckssss commented on GitHub (Aug 31, 2025):

same here. two devices:
OnePlus 12 OxygenOS 15 (Android 15) bitwarden 2024.08.0
and
Nothing Phone 2 NothingOS3 (android 15) bitwarden 2024.08.0

very annoying

<!-- gh-comment-id:3240338686 --> @buckssss commented on GitHub (Aug 31, 2025): same here. two devices: OnePlus 12 OxygenOS 15 (Android 15) bitwarden 2024.08.0 and Nothing Phone 2 NothingOS3 (android 15) bitwarden 2024.08.0 very annoying
GiteaMirror commented 2026-05-01 12:55:23 -05:00
Author
Owner
Copy Link

@NoxArt commented on GitHub (Sep 2, 2025):

I have 1 hour timeout and still repro

© Bitwarden Inc. 2015-2025

Version: 2025.8.0 (20577)
📱 samsung SM-S908B 🤖 15@35 📦 prod
🧱 commit: bitwarden/android/release/2025.8-rc32@1c525b9dfc588105e1fd8f3ad2d4196803c19cd7
💻 build source: bitwarden/android/actions/runs/16834718954/attempts/1
🦀 SDK: 1.0.0-2450-9fe3aeda
🌩 Server: 2025.8.0 @ EU

<!-- gh-comment-id:3243800037 --> @NoxArt commented on GitHub (Sep 2, 2025): I have 1 hour timeout and still repro © Bitwarden Inc. 2015-2025 Version: 2025.8.0 (20577) 📱 samsung SM-S908B 🤖 15@35 📦 prod 🧱 commit: bitwarden/android/release/2025.8-rc32@1c525b9dfc588105e1fd8f3ad2d4196803c19cd7 💻 build source: bitwarden/android/actions/runs/16834718954/attempts/1 🦀 SDK: 1.0.0-2450-9fe3aeda 🌩 Server: 2025.8.0 @ EU
GiteaMirror commented 2026-05-01 12:55:27 -05:00
Author
Owner
Copy Link

@reinob commented on GitHub (Sep 2, 2025):

as above. The only working workaround is to set the timeout to "never", with its security implications.

<!-- gh-comment-id:3245272403 --> @reinob commented on GitHub (Sep 2, 2025): as above. The only working workaround is to set the timeout to "never", with its security implications.
GiteaMirror commented 2026-05-01 12:55:30 -05:00
Author
Owner
Copy Link

@pamperer562580892423 commented on GitHub (Sep 2, 2025):

as above. The only working workaround is to set the timeout to "never", with its security implications.

I have another workaround, that works for me: just try it a second time, and then the "login will not disappear".

<!-- gh-comment-id:3245711381 --> @pamperer562580892423 commented on GitHub (Sep 2, 2025): > as above. The only working workaround is to set the timeout to "never", with its security implications. I have another workaround, that works for me: just try it a second time, and then the "login will not disappear".
GiteaMirror commented 2026-05-01 12:55:32 -05:00
Author
Owner
Copy Link

@n0k0m3 commented on GitHub (Sep 2, 2025):

Solution is to downgrade to 2025.7.2 until we get some resolution from bitwarden team

<!-- gh-comment-id:3245760135 --> @n0k0m3 commented on GitHub (Sep 2, 2025): Solution is to downgrade to 2025.7.2 until we get some resolution from bitwarden team
GiteaMirror commented 2026-05-01 12:55:34 -05:00
Author
Owner
Copy Link

@reinob commented on GitHub (Sep 3, 2025):

I just installed 2025.8.1 (directly off github) and it seems that this issue is solved!

<!-- gh-comment-id:3249037126 --> @reinob commented on GitHub (Sep 3, 2025): I just installed 2025.8.1 (directly off github) and it seems that this issue is solved!
GiteaMirror commented 2026-05-01 12:55:36 -05:00
Author
Owner
Copy Link

@ilijaruzic commented on GitHub (Sep 3, 2025):

2025.8.1 fixed it for me as well (Android 15, S24U, immediate session timeout).

<!-- gh-comment-id:3250360967 --> @ilijaruzic commented on GitHub (Sep 3, 2025): 2025.8.1 fixed it for me as well (Android 15, S24U, immediate session timeout).
GiteaMirror commented 2026-05-01 12:55:38 -05:00
Author
Owner
Copy Link

@SaintPatrck commented on GitHub (Sep 3, 2025):

Thank you all for your patience while we addressed the issue.

As some of you have already noticed, we released 2025.8.1 early to get it fixed. It is actively rolling out in Play Store and is already available in our F-Droid repository so I'll be closing this ticket.

Unfortunately we were not able to find a solution that completely retained our fix for the navigation bar appearance which manifests in some revisions of Android 15.

However, now that autofill is working properly you should be able to use Card autofill which was fixed and improved in 2025.8.0. This fills a gap for Chromium users who lost Card autofill after enabling 3rd party credential providers. 🥳

<!-- gh-comment-id:3250809002 --> @SaintPatrck commented on GitHub (Sep 3, 2025): Thank you all for your patience while we addressed the issue. As some of you have already noticed, we released 2025.8.1 early to get it fixed. It is actively rolling out in Play Store and is already available in our F-Droid repository so I'll be closing this ticket. Unfortunately we were not able to find a solution that completely retained our fix for the navigation bar appearance which manifests in some revisions of Android 15. However, now that autofill is working properly you should be able to use Card autofill which was fixed and improved in 2025.8.0. This fills a gap for Chromium users who lost Card autofill after enabling 3rd party credential providers. 🥳
GiteaMirror commented 2026-05-01 12:55:41 -05:00
Author
Owner
Copy Link

@infinitytec commented on GitHub (Sep 9, 2025):

Just wanted to say thanks to the Bitwarden team for addressing and resolving this issue!

<!-- gh-comment-id:3270300439 --> @infinitytec commented on GitHub (Sep 9, 2025): Just wanted to say thanks to the Bitwarden team for addressing and resolving this issue!
GiteaMirror commented 2026-05-01 12:55:43 -05:00
Author
Owner
Copy Link

@wvonghack commented on GitHub (Sep 22, 2025):

Looks like this problem has re-surfaced again. Bitwarden doesn't show up anymore.

<!-- gh-comment-id:3317067929 --> @wvonghack commented on GitHub (Sep 22, 2025): Looks like this problem has re-surfaced again. Bitwarden doesn't show up anymore.
GiteaMirror commented 2026-05-01 12:55:46 -05:00
Author
Owner
Copy Link

@dg1234567 commented on GitHub (Sep 22, 2025):

I've had the opposite. Problem appears to be solved.

<!-- gh-comment-id:3318447325 --> @dg1234567 commented on GitHub (Sep 22, 2025): I've had the opposite. Problem appears to be solved.
GiteaMirror commented 2026-05-01 12:55:48 -05:00
Author
Owner
Copy Link

@pamperer562580892423 commented on GitHub (Sep 22, 2025):

I've posted this in two other related issues as well - but here again as it seems relevant also:

I would like to add a few things here. First, there are two things that @dwbit shared first on the Community Forum (and probably also on Reddit etc.):

  • If you previously changed any browser autofill feature flags (chrome://flags, brave://flags…) – an older recommendation/necessity from 2023/2024 --, you may need to reset them now to the default flag settings to prevent autofill from breaking with the new Chrome autofill framework.

  • And there also is a new current bug on the Chromium browsers side – but on Chrome 141 BETA you can enable the following flag: #autofill-update-context-for-web-contents (chrome://flags). Eventually only browser updates will fix this bug.

There is also a new short guide about Autofill on Android, which collects all current "tips" etc.: https://community.bitwarden.com/t/short-guide-tips-autofill-on-android/88941/

PS: @wvonghack I think the mentioned "Chromium bug" leads to "loosing autofill" intermittently, so that could be a reason for what you are experiencing now.

<!-- gh-comment-id:3318526421 --> @pamperer562580892423 commented on GitHub (Sep 22, 2025): I've posted this in two other related issues as well - but here again as it seems relevant also: I would like to add a few things here. First, there are two things that @dwbit shared first on the Community Forum (and probably also on Reddit etc.): - If you previously changed any browser autofill **feature flags** (chrome://flags, brave://flags…) – an older recommendation/necessity from 2023/2024 --, you may need to reset them now to the default flag settings to prevent autofill from breaking with the new Chrome autofill framework. - And there also is a new [current bug](https://issuetracker.google.com/issues/439553272) on the Chromium browsers side – but on Chrome 141 BETA you can enable the following flag: #autofill-update-context-for-web-contents (chrome://flags). Eventually only browser updates will fix this bug. There is also a new short guide about Autofill on Android, which collects all current "tips" etc.: https://community.bitwarden.com/t/short-guide-tips-autofill-on-android/88941/ PS: @wvonghack I think the mentioned "Chromium bug" leads to "loosing autofill" intermittently, so that could be a reason for what you are experiencing now.
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 app:password-manager 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#50413
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?