github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-03-22 20:41:29 -05:00
Code Issues 144 Packages Projects Releases 118 Wiki Activity

App freeze after Unlock using master password if your impatient #2259

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

Originally created by @shift18 on GitHub (Jun 17, 2025).

Steps To Reproduce

How to replicate intermittent freezing of app

You've previously logged in to bitwarden on android and locked the app but your still logged in.

  1. Open bitwarden
  2. Enter master password
  3. Press unlock button
  4. Wait until vault is almost unlocked (Your vault takes a while to unlock as you've increased the number of rounds of encryption)
    Once bitwarden is almost done opening your vault you press the unlock button once more as you're impaintient.

Expected Result

Uhm, not freeze, especially once the wallet is open

Actual Result

Bitwarden freezes for a moment every few seconds after unlocking.
Does not seem to ever go away unless bitwarden is closed fully.

Screenshots or Videos

Snippet from logcat, complete logcat available to devs. On request

type: ANR
osVersion: google/bluejay/bluejay:15/BP1A.250505.005/2025061600:user/release-keys
userType: full.secondary
package: com.x8bit.bitwarden:20269, targetSdk 35
process: com.x8bit.bitwarden
installer: com.android.vending

Subject: Input dispatching timed out (688f496 com.x8bit.bitwarden/com.x8bit.bitwarden.MainActivity is not responding. Waited 5003ms for MotionEvent).
RssHwmKb: 1312496
RssKb: 1310136
RssAnonKb: 1135692
RssShmemKb: 896
VmSwapKb: 0


--- CriticalEventLog ---
capacity: 20
events <
  timestamp_ms: 1750187111888
  anr <
    pid: 26652
    process: "com.x8bit.bitwarden"
    process_class: 1
    subject: "Input dispatching timed out (32ea272 com.x8bit.bitwarden/com.x8bit.bitwarden.MainActivity is not responding. Waited 5001ms for MotionEvent)."
    uid: 1610187
  >
>
events <
  timestamp_ms: 1750187251765
  anr <
    pid: 28928
    process: "com.x8bit.bitwarden"
    process_class: 1
    subject: "Input dispatching timed out (3ab566b com.x8bit.bitwarden/com.x8bit.bitwarden.MainActivity is not responding. Waited 5001ms for MotionEvent)."
    uid: 1610187

Additional Context

Been happening for many months, not a new bug.

Build Version

2025.5

What server are you connecting to?

US

Self-host Server Version

No response

Environment Details

Pixel 6a
GOS:2025061600

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 @shift18 on GitHub (Jun 17, 2025). ### Steps To Reproduce ### How to replicate intermittent freezing of app **You've previously logged in to bitwarden on android and locked the app but your still logged in.** 1. Open bitwarden 2. Enter master password 3. Press unlock button 4. Wait until vault is almost unlocked (**Your vault takes a while to unlock as you've increased the number of rounds of encryption**) Once bitwarden is almost done opening your vault you press the unlock button once more as you're impaintient. ### Expected Result Uhm, not freeze, especially once the wallet is open ### Actual Result Bitwarden freezes for a moment every few seconds after unlocking. Does not seem to ever go away unless bitwarden is closed fully. ### Screenshots or Videos Snippet from logcat, complete logcat available to devs. On request ``` type: ANR osVersion: google/bluejay/bluejay:15/BP1A.250505.005/2025061600:user/release-keys userType: full.secondary package: com.x8bit.bitwarden:20269, targetSdk 35 process: com.x8bit.bitwarden installer: com.android.vending Subject: Input dispatching timed out (688f496 com.x8bit.bitwarden/com.x8bit.bitwarden.MainActivity is not responding. Waited 5003ms for MotionEvent). RssHwmKb: 1312496 RssKb: 1310136 RssAnonKb: 1135692 RssShmemKb: 896 VmSwapKb: 0 --- CriticalEventLog --- capacity: 20 events < timestamp_ms: 1750187111888 anr < pid: 26652 process: "com.x8bit.bitwarden" process_class: 1 subject: "Input dispatching timed out (32ea272 com.x8bit.bitwarden/com.x8bit.bitwarden.MainActivity is not responding. Waited 5001ms for MotionEvent)." uid: 1610187 > > events < timestamp_ms: 1750187251765 anr < pid: 28928 process: "com.x8bit.bitwarden" process_class: 1 subject: "Input dispatching timed out (3ab566b com.x8bit.bitwarden/com.x8bit.bitwarden.MainActivity is not responding. Waited 5001ms for MotionEvent)." uid: 1610187 ``` ### Additional Context Been happening for many months, not a new bug. ### Build Version 2025.5 ### What server are you connecting to? US ### Self-host Server Version _No response_ ### Environment Details Pixel 6a GOS:2025061600 ### 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:13:32 -06:00
GiteaMirror commented 2025-11-26 23:13:33 -06:00
Author
Owner
Copy Link

@bitwarden-bot commented on GitHub (Jun 17, 2025):

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

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

@Greenderella commented on GitHub (Jun 19, 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!

Issue c

@Greenderella commented on GitHub (Jun 19, 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! Issue c
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#2259
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?