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

[PM-27159] Inconsistently, RFC 6238 generations are not replaced in the UI when PT30S elapses, until the entrant is re-accessed. #2366

New Issue
Open
opened 2025-11-26 23:16:55 -06:00 by GiteaMirror · 2 comments
GiteaMirror commented 2025-11-26 23:16:55 -06:00
Owner
Copy Link

Originally created by @RokeJulianLockhart on GitHub (Oct 13, 2025).

Steps To Reproduce

  1. Create an item with a TOTP key:

    #!/usr/bin/env sh
bw create item "$(jq -n \
	--arg name "Example Service" \
	--arg totp "otpauth://totp/Example:user@example.com?secret=JBSWY3DPEHPK3PXP&issuer=Example&algorithm=SHA1&digits=6&period=30" \
	'{type:1, name:$name, login:{username:$username, password:$password, totp:$totp}}')" \
	--session "$BW_SESSION"

    That's merely an example. It's not prescriptive.

  2. Visit it in com.x8bit.bitwarden/.MainActivity.

  3. Wait PT30S.

Expected Result

The generated code should have been replaced.

Actual Result

The code did not refresh, until I closed, then re-accessed, the vault entrant.

Screenshots or Videos

This was infeasible when it occurred, per community.bitwarden.com/t/317/15.

Build Version

versionName=2025.9.1
versionCode=20742

What server are you connecting to?

US

Server Version

Server version: 2025.9.2

Environment Details

Device

[ro.product.brand]: [Fairphone]
[ro.build.product]: [FP5]

OS Version

[ro.build.version.release]: [15]
[ro.build.display.id]: [FP5.VT28.C.042.20250623]

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 @RokeJulianLockhart on GitHub (Oct 13, 2025). ### Steps To Reproduce 1. Create an item with a TOTP key: ~~~sh #!/usr/bin/env sh bw create item "$(jq -n \ --arg name "Example Service" \ --arg totp "otpauth://totp/Example:user@example.com?secret=JBSWY3DPEHPK3PXP&issuer=Example&algorithm=SHA1&digits=6&period=30" \ '{type:1, name:$name, login:{username:$username, password:$password, totp:$totp}}')" \ --session "$BW_SESSION" ~~~ That's merely an example. It's not prescriptive. 1. Visit it in `com.x8bit.bitwarden/.MainActivity`. 1. Wait PT30S. ### Expected Result The generated code should have been replaced. ### Actual Result The code did not refresh, until I closed, then re-accessed, the vault entrant. ### Screenshots or Videos This was infeasible when it occurred, per [`community.bitwarden.com/t/317/15`](https://community.bitwarden.com/t/option-to-allow-screenshots/317/15?u=rokejulianlockhart). <!-- ### Additional Context _No response_ --> ### Build Version > ~~~ini > versionName=2025.9.1 > versionCode=20742 > ~~~ ### What server are you connecting to? US ### Server Version > ~~~YAML > Server version: 2025.9.2 > ~~~ ### Environment Details #### Device > ~~~YAML > [ro.product.brand]: [Fairphone] > [ro.build.product]: [FP5] > ~~~ #### OS Version > ~~~YAML > [ro.build.version.release]: [15] > [ro.build.display.id]: [FP5.VT28.C.042.20250623] > ~~~ ### 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:password-managerbug labels 2025-11-26 23:16:55 -06:00
GiteaMirror commented 2025-11-26 23:16:56 -06:00
Author
Owner
Copy Link

@bitwarden-bot commented on GitHub (Oct 20, 2025):

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

@bitwarden-bot commented on GitHub (Oct 20, 2025): Thank you for your report! We've added this to our internal board for review. ID: PM-27159
GiteaMirror commented 2025-11-26 23:16:56 -06:00
Author
Owner
Copy Link

@rmcdowell-bitwarden commented on GitHub (Oct 21, 2025):

Hi there,

This issue has been escalated for further investigation. If you have more information that can help us, please add it below.

Thanks!

@rmcdowell-bitwarden commented on GitHub (Oct 21, 2025): Hi there, This issue 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: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#2366
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?