[GH-ISSUE #6079] [PM-27374] ANR occurs when "Send crash logs" setting is disabled #77465

Closed
opened 2026-05-19 14:17:47 -05:00 by GiteaMirror · 5 comments
Owner

Originally created by @okotowarishimasu on GitHub (Oct 25, 2025).
Original GitHub issue: https://github.com/bitwarden/android/issues/6079

Steps To Reproduce

  1. Open Bitwarden Android app
  2. Go to Settings
  3. Disable "Send crash logs" option
  4. Use the app for several days
  5. ANR (Application Not Responding) error occurs

Expected Result

The app should work normally regardless of crash log settings.

Actual Result

ANR occurs when "Send crash logs" is OFF.
When I enable "Send crash logs", the issue is resolved immediately.

Screenshots or Videos

No response

Additional Context

The issue does not occur every time the setting is OFF. It appears to develop over time.

Hypothesis: Crash logs may be accumulating in local storage without proper rotation when the setting is OFF. Enabling the setting sends and clears these logs.

Build Version

2025.10.0 (20794)

What server are you connecting to?

US

Self-host Server Version

No response

Environment Details

  • Android version: [15]
  • Device: [XQ-DC44 (Xperia 10 V)]
  • Bitwarden version: [2025.10.0(20794)]
  • Using AdGuard (Bitwarden excluded from routing)

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 @okotowarishimasu on GitHub (Oct 25, 2025). Original GitHub issue: https://github.com/bitwarden/android/issues/6079 ### Steps To Reproduce 1. Open Bitwarden Android app 2. Go to Settings 3. Disable "Send crash logs" option 4. Use the app for several days 5. ANR (Application Not Responding) error occurs ### Expected Result The app should work normally regardless of crash log settings. ### Actual Result ANR occurs when "Send crash logs" is OFF. When I enable "Send crash logs", the issue is resolved immediately. ### Screenshots or Videos _No response_ ### Additional Context The issue does not occur every time the setting is OFF. It appears to develop over time. Hypothesis: Crash logs may be accumulating in local storage without proper rotation when the setting is OFF. Enabling the setting sends and clears these logs. ### Build Version 2025.10.0 (20794) ### What server are you connecting to? US ### Self-host Server Version _No response_ ### Environment Details - Android version: [15] - Device: [XQ-DC44 (Xperia 10 V)] - Bitwarden version: [2025.10.0(20794)] - Using AdGuard (Bitwarden excluded from routing) ### 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-19 14:17:47 -05:00
Author
Owner

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

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

<!-- gh-comment-id:3445390991 --> @bitwarden-bot commented on GitHub (Oct 25, 2025): Thank you for your report! We've added this to our internal board for review. ID: PM-27374
Author
Owner

@rmcdowell-bitwarden commented on GitHub (Oct 27, 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:3449129888 --> @rmcdowell-bitwarden commented on GitHub (Oct 27, 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!
Author
Owner

@okotowarishimasu commented on GitHub (Mar 11, 2026):

I have confirmed that this issue no longer occurs in app version 2026.2.1 (21297).
Could you please close this issue? Thank you.

<!-- gh-comment-id:4039027861 --> @okotowarishimasu commented on GitHub (Mar 11, 2026): I have confirmed that this issue no longer occurs in app version 2026.2.1 (21297). Could you please close this issue? Thank you.
Author
Owner

@pamperer562580892423 commented on GitHub (Mar 11, 2026):

@okotowarishimasu Just FYI, as the author you should also be able to close this issue yourself.

<!-- gh-comment-id:4039471627 --> @pamperer562580892423 commented on GitHub (Mar 11, 2026): @okotowarishimasu Just FYI, as the author you should also be able to close this issue yourself.
Author
Owner

@okotowarishimasu commented on GitHub (Mar 11, 2026):

I initially asked the maintainers to close this issue just in case it needed to be synced with Bitwarden's internal tracking system. However, since that doesn't seem to be necessary.
Closing.

<!-- gh-comment-id:4041400457 --> @okotowarishimasu commented on GitHub (Mar 11, 2026): I initially asked the maintainers to close this issue just in case it needed to be synced with Bitwarden's internal tracking system. However, since that doesn't seem to be necessary. Closing.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#77465