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

[GH-ISSUE #6244] [BWA-209] VaultVerificationCodeItem are frozen and not updated after getting back to the app #15038

New Issue
Open
opened 2026-04-15 01:19:55 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-15 01:19:55 -05:00
Owner
Copy Link

Originally created by @tajchert on GitHub (Dec 7, 2025).
Original GitHub issue: https://github.com/bitwarden/android/issues/6244

Steps To Reproduce

  1. Open Authenticator app with some TOTP codes setup.
  2. Wait till screen timeout and device lock (ex. 30s).
  3. Quickly unlock device (Authenticator will be displayed as it was last app).

Expected Result

TOTP codes should continue countdown.

Actual Result

In some edge cases after getting back to the Authenticator app countdown was frozen (ex. on 9s) and refreshed only on next TOTP code change.

Screenshots or Videos

Sorry, despite my best efforts I wasn't able to record this. This happened twice in my case. I belive quick unlock of device just after screen is locked due to lack of activity is key to reproducing this scenario.

Additional Context

Authenticator seems to use Flow, and Password Manager seems to use StateFlow. Also Authenticator seems to have with some "artificial" delay to stop upstream flow and can use stale stateIn before all flows emit their values (usage of combine()).

Build Version

2025.10.2

What server are you connecting to?

US

Self-host Server Version

No response

Environment Details

  • Device: OnePlus 15
  • OS: Android 16 (CPH2747_16.0.1.303(EX01))

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 @tajchert on GitHub (Dec 7, 2025). Original GitHub issue: https://github.com/bitwarden/android/issues/6244 ### Steps To Reproduce 1. Open Authenticator app with some TOTP codes setup. 2. Wait till screen timeout and device lock (ex. 30s). 3. Quickly unlock device (Authenticator will be displayed as it was last app). ### Expected Result TOTP codes should continue countdown. ### Actual Result In some edge cases after getting back to the Authenticator app countdown was frozen (ex. on 9s) and refreshed only on next TOTP code change. ### Screenshots or Videos Sorry, despite my best efforts I wasn't able to record this. This happened twice in my case. I belive quick unlock of device just after screen is locked due to lack of activity is key to reproducing this scenario. ### Additional Context Authenticator seems to use Flow, and Password Manager seems to use StateFlow. Also Authenticator seems to have with some "artificial" delay to stop upstream flow and can use stale stateIn before all flows emit their values (usage of `combine()`). ### Build Version 2025.10.2 ### What server are you connecting to? US ### Self-host Server Version _No response_ ### Environment Details - Device: OnePlus 15 - OS: Android 16 (CPH2747_16.0.1.303(EX01)) ### 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 app:authenticatorbug labels 2026-04-15 01:19:55 -05:00
GiteaMirror commented 2026-04-15 01:19:56 -05:00
Author
Owner
Copy Link

@bitwarden-bot commented on GitHub (Dec 7, 2025):

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

<!-- gh-comment-id:3621870303 --> @bitwarden-bot commented on GitHub (Dec 7, 2025): Thank you for your report! We've added this to our internal board for review. ID: [BWA-209](https://bitwarden.atlassian.net/browse/BWA-209) [BWA-209]: https://bitwarden.atlassian.net/browse/BWA-209?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ
GiteaMirror commented 2026-04-15 01:19:57 -05:00
Author
Owner
Copy Link

@rmcdowell-bitwarden commented on GitHub (Dec 8, 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:3624330036 --> @rmcdowell-bitwarden commented on GitHub (Dec 8, 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!
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:authenticator 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#15038
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?