github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-08-28 14:47:37 -05:00
Code Issues 2.4k Packages Projects Releases 129 Wiki Activity

[GH-ISSUE #3207] During synchronisation, the frequency of ANRs directly correlates with the quantity of entries in the user's vault and the RAM available. #88293

New Issue
Closed
opened 2026-05-26 21:18:14 -05:00 by GiteaMirror · 8 comments
GiteaMirror commented 2026-05-26 21:18:14 -05:00
Owner
Copy Link
Copy Source

Originally created by @RokeJulianLockhart on GitHub (Apr 29, 2024).
Original GitHub issue: https://github.com/bitwarden/android/issues/3207

Steps To Reproduce

  1. Install the OS

    1. The Fairphone 4

      1. fairphone-android-builds.ams3.digitaloceanspaces.com/FP4/A13/FP4-TP2D-factory.zip or

      2. calyxos.org/install/devices/FP4/linux/#run-device-flasher.

    2. The Google Pixel 3

      I've confirmed it with calyxos.org/install/devices/blueline/linux/#run-device-flasher.

  2. Install the Bitwarden AOSP package

    1. 2024.4.1 from play.google.com/store/apps/details?id=com.x8bit.bitwarden.

    2. mobileapp.bitwarden.com/fdroid/repo/com.x8bit.bitwarden-fdroid.apk from mobileapp.bitwarden.com/fdroid/repo/com.x8bit.bitwarden-fdroid.apk.

    v2024.4.0/Bitwarden.iOS.zip is unaffected, alongside the alternative clients:

    1. web-v2024.4.1

    2. desktop-v2024.4.1

  3. Login with the account identified by the fingerprint phrase overuse-definite-poach-almanac-dorsal.

Expected Result

I expect to be able to utilize Bitwarden with the same speed I would any other account.

Actual Result

I am informed every 5 seconds that Bitwarden has crashed.

Screenshots or Videos

https://github.com/bitwarden/mobile/assets/42837531/41110354-d867-4b76-ad85-57826b5f0ea2

image

Additional Context

I have +2056 vault entries, which appears to be the sole differentiator between my account (which is affected) and others' accounts, which aren't affected, even on the same device and installation. I've limited my vault.bitwarden.com/#/settings/security/security-keys to 5000 (the minimum available) yet this didn't modify the behaviour whatsoever. AChep/keyguard-app/releases/download/r20240417/androidApp-none-release.apk does not display this behaviour, although it struggles to synchronize my vault.

I've included an adb bugreport at bugreport-FP5-TKQ1.230127.002-2024-04-29-15-11-35.zip, because source.android.com/docs/core/tests/debug/read-bug-reports#event-log indicates that it might be useful.

Operating System

Android

Operating System Version

androidapp://com.android.settings reports FP5.TT4C.A.154.20240320.

Device

Fairphone FP5

Build Version

v2024.4.0/com.x8bit.bitwarden-fdroid.apk

Beta

  • Using a pre-release version of the application.
Originally created by @RokeJulianLockhart on GitHub (Apr 29, 2024). Original GitHub issue: https://github.com/bitwarden/android/issues/3207 ### Steps To Reproduce 1. #### **Install the OS** 1. #### **The Fairphone 4** 1. [`fairphone-android-builds.ams3.digitaloceanspaces.com/FP4/A13/FP4-TP2D-factory.zip`](https://fairphone-android-builds.ams3.digitaloceanspaces.com/FP4/A13/FP4-TP2D-factory.zip) or 1. [`calyxos.org/install/devices/FP4/linux/#run-device-flasher`](https://calyxos.org/install/devices/FP4/linux/#run-device-flasher). 1. #### **The Google Pixel 3** I've confirmed it with [`calyxos.org/install/devices/blueline/linux/#run-device-flasher`](https://calyxos.org/install/devices/blueline/linux/#run-device-flasher). 1. #### **Install the Bitwarden AOSP package** 1. [`2024.4.1`](https://www.apkmirror.com/apk/bitwarden-inc/bitwarden-password-manager/bitwarden-password-manager-2024-4-1-release/bitwarden-password-manager-2024-4-1-android-apk-download/) from [`play.google.com/store/apps/details?id=com.x8bit.bitwarden`](https://play.google.com/store/apps/details?id=com.x8bit.bitwarden&hl=en&gl=US). 1. [`mobileapp.bitwarden.com/fdroid/repo/com.x8bit.bitwarden-fdroid.apk`](https://github.com/bitwarden/mobile/releases/download/v2024.4.0/com.x8bit.bitwarden-fdroid.apk) from [`mobileapp.bitwarden.com/fdroid/repo/com.x8bit.bitwarden-fdroid.apk`](https://mobileapp.bitwarden.com/fdroid/repo/com.x8bit.bitwarden-fdroid.apk). [`v2024.4.0/Bitwarden.iOS.zip`](https://github.com/bitwarden/mobile/releases/download/v2024.4.0/Bitwarden.iOS.zip) is unaffected, alongside the alternative clients: 1. [`web-v2024.4.1`](https://github.com/bitwarden/clients/releases/tag/web-v2024.4.1) 1. [`desktop-v2024.4.1`](https://github.com/bitwarden/clients/releases/tag/desktop-v2024.4.1) 1. Login with the account identified by the fingerprint phrase `overuse-definite-poach-almanac-dorsal`. ### Expected Result I expect to be able to utilize Bitwarden with the same speed I would any other account. ### Actual Result I am informed every 5 seconds that Bitwarden has crashed. ### Screenshots or Videos https://github.com/bitwarden/mobile/assets/42837531/41110354-d867-4b76-ad85-57826b5f0ea2 <details> ![image](https://github.com/bitwarden/mobile/assets/42837531/46349ed8-5dcb-47dd-a738-b24e72b996be) <!-- [^1] [^2]: https://vault.bitwarden.com/#/vault?search=test&itemId=69443889-3c11-4f1d-96c1-b16100e5d601 --> </details> ### Additional Context I have +2056 vault entries, which appears to be the sole differentiator between my account (which is affected) and others' accounts, which aren't affected, even on the same device and installation. I've limited my [`vault.bitwarden.com/#/settings/security/security-keys`](https://vault.bitwarden.com/#/settings/security/security-keys) to 5000 (the minimum available) yet this didn't modify the behaviour whatsoever. [`AChep/keyguard-app/releases/download/r20240417/androidApp-none-release.apk`](https://github.com/AChep/keyguard-app/releases/download/r20240417/androidApp-none-release.apk) does not display this behaviour, although it struggles to synchronize my vault. I've included an [`adb bugreport`](https://developer.android.com/studio/debug/bug-report#bugreport) at [`bugreport-FP5-TKQ1.230127.002-2024-04-29-15-11-35.zip`](https://github.com/bitwarden/mobile/files/15150631/bugreport-FP5-TKQ1.230127.002-2024-04-29-15-11-35.zip), because [`source.android.com/docs/core/tests/debug/read-bug-reports#event-log`](https://source.android.com/docs/core/tests/debug/read-bug-reports#event-log) indicates that it might be useful. ### Operating System Android ### Operating System Version `androidapp://com.android.settings` reports `FP5.TT4C.A.154.20240320`. ### Device [Fairphone FP5][1] [1]: https://www.wikidata.org/w/index.php?title=Q122070914&oldid=2362479558#firstHeading:~:text=Random%20Lexeme-,Fairphone%205,-5G%20(Q122070914) ### Build Version [`v2024.4.0/com.x8bit.bitwarden-fdroid.apk`][2] [2]: https://github.com/bitwarden/mobile/releases/download/v2024.4.0/com.x8bit.bitwarden-fdroid.apk ### Beta - [ ] Using a pre-release version of the application.
GiteaMirror added the bug label 2026-05-26 21:18:14 -05:00
GiteaMirror commented 2026-05-26 21:18:17 -05:00
Author
Owner
Copy Link
Copy Source

@Krychaz commented on GitHub (Apr 30, 2024):

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:2085453388 --> @Krychaz commented on GitHub (Apr 30, 2024): 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-26 21:18:18 -05:00
Author
Owner
Copy Link
Copy Source

@RokeJulianLockhart commented on GitHub (Apr 30, 2024):

https://github.com/bitwarden/mobile/issues/3207#issuecomment-2085453388

@Krychaz, I'm not surprised - it solely appears to affect my account. If I remove my account and add another's, or merely switch to another's with mine added, it doesn't appear. It also doesn't appear in any client except the AOSP application. It also solely occurs when synchronisation is involved - if I do not initiate a sync (like by modifying an entry or explicitly invoking one) it also doesn't appear. I'm confident that it's due to the amount of credentials in my account.

I've been experiencing this worsening for almost a year now, on 3 AOSP-based OSes, so I'm convinced that it's a problem with the client.

<!-- gh-comment-id:2085891491 --> @RokeJulianLockhart commented on GitHub (Apr 30, 2024): > https://github.com/bitwarden/mobile/issues/3207#issuecomment-2085453388 @Krychaz, I'm not surprised - it solely appears to affect my account. If I remove my account and add another's, or merely switch to another's with mine added, it doesn't appear. It also doesn't appear in any client except the AOSP application. It also solely occurs when synchronisation is involved - if I do not initiate a sync (like by modifying an entry or explicitly invoking one) it also doesn't appear. I'm confident that it's due to the amount of credentials in my account. I've been experiencing this worsening for almost a year now, on 3 AOSP-based OSes, so I'm convinced that it's a problem with the client.
GiteaMirror commented 2026-05-26 21:18:19 -05:00
Author
Owner
Copy Link
Copy Source

@Freebase394 commented on GitHub (May 5, 2024):

@RokeJulianLockhart Hi guys. It's true.
Hi everyone, unfortunately it's true, I've been a Bitwarden user for over 3 years or more(I came from LastPass) and I confess that since I purchased this smartphone about 2 months ago, Fossibot 101P (only P Version, not "PRO") Version 2023 new with the Android 13 operating system, on this Android it freezes a lot and most of the time when I log in, I have to enter the credentials 3 / 4 or even 5 times, other times be sure to close all the apps on the background, but background apps its not the problem, im ALWAYS with free memoRY RAM, all this to be able to log in to my account with around 600 / 700 credential entries... let's say there aren't that many... I have other devices that are even weaker, another Samsung J7 DUOS 2017 even with Android 9, 4 GB of RAM and it works much better than this Fossibot that I have at the moment.
please tell me how I can help, from debugging the APP, sending reports, among other things, to maintaining and contributing to this small and at the same time BIG problem, I don't know if this problem always existed, or just started to exist from some specific version until now. But I believe that everything has a solution. Please count on me

Operating System
Android 13

Device Model Name
Fossibot F101 P

Operating System Version
FOSSiBOT_F101_E_V05_20240123

<!-- gh-comment-id:2094983964 --> @Freebase394 commented on GitHub (May 5, 2024): @RokeJulianLockhart Hi guys. It's true. Hi everyone, unfortunately it's true, I've been a Bitwarden user for over 3 years or more(I came from LastPass) and I confess that since I purchased this smartphone about 2 months ago, Fossibot 101P (only P Version, not "PRO") Version 2023 new with the Android 13 operating system, on this Android it freezes a lot and most of the time when I log in, I have to enter the credentials 3 / 4 or even 5 times, other times be sure to close all the apps on the background, but background apps its not the problem, im ALWAYS with free memoRY RAM, all this to be able to log in to my account with around 600 / 700 credential entries... let's say there aren't that many... I have other devices that are even weaker, another Samsung J7 DUOS 2017 even with Android 9, 4 GB of RAM and it works much better than this Fossibot that I have at the moment. please tell me how I can help, from debugging the APP, sending reports, among other things, to maintaining and contributing to this small and at the same time BIG problem, I don't know if this problem always existed, or just started to exist from some specific version until now. But I believe that everything has a solution. Please count on me Operating System Android 13 Device Model Name Fossibot F101 P Operating System Version FOSSiBOT_F101_E_V05_20240123
GiteaMirror commented 2026-05-26 21:18:19 -05:00
Author
Owner
Copy Link
Copy Source

@RokeJulianLockhart commented on GitHub (May 5, 2024):

https://github.com/bitwarden/mobile/issues/3207#issuecomment-2094983964

@Freebase394, until they respond, another adb bugreport and a display recording from you would be useful for mere comparison, at least. Many thanks for the corroboration and point of reference regarding OS versions. This may well have commenced approximately when my FP4 upgraded its OS (although my credential entries were exponentially increasing at that time too).

<!-- gh-comment-id:2094985410 --> @RokeJulianLockhart commented on GitHub (May 5, 2024): > https://github.com/bitwarden/mobile/issues/3207#issuecomment-2094983964 @Freebase394, ~~until they respond, another [`adb bugreport`](https://developer.android.com/studio/debug/bug-report#bugreportdevice) and a display recording from you would be useful for mere comparison, at least.~~ Many thanks for the corroboration and point of reference regarding OS versions. This may well have commenced approximately when my FP4 upgraded its OS (although my credential entries were exponentially increasing at that time too).
GiteaMirror commented 2026-05-26 21:18:21 -05:00
Author
Owner
Copy Link
Copy Source

@RokeJulianLockhart commented on GitHub (May 10, 2024):

https://github.com/bitwarden/mobile/issues/3207#issuecomment-2094983964

@Freebase394, you appear to have correctly estimated the cause (albeit, expectedly, not to sufficient standard to know what ultimately causes this) – the specifications of the device.

To demonstrate, I have installed kojipkgs.fedoraproject.org's waydroid-1.4.2-3.fc40.noarch 1 and v2024.4.2/com.x8bit.bitwarden.apk on my powerful desktop system, and the issue does not occur! However, that same configuration (albeit using build.alpinelinux.org's waydroid-1.4.2-r5) on my FP4 running postmarketOS exhibits the behaviour, as does my CalyxOS Google Pixel 3, and stock FP5.

<!-- gh-comment-id:2104850715 --> @RokeJulianLockhart commented on GitHub (May 10, 2024): > https://github.com/bitwarden/mobile/issues/3207#issuecomment-2094983964 @Freebase394, you appear to have correctly estimated the cause (albeit, expectedly, not to sufficient standard to know what *ultimately* causes this) – the specifications of the device. To demonstrate, I have installed [`kojipkgs.fedoraproject.org`'s `waydroid-1.4.2-3.fc40.noarch`](https://kojipkgs.fedoraproject.org//packages/waydroid/1.4.2/3.fc40/noarch/waydroid-1.4.2-3.fc40.noarch.rpm) [^1] and [`v2024.4.2/com.x8bit.bitwarden.apk`](https://github.com/bitwarden/mobile/releases/download/v2024.4.2/com.x8bit.bitwarden.apk) on my powerful desktop system, and the issue does not occur! However, that same configuration (albeit using [`build.alpinelinux.org`'s `waydroid-1.4.2-r5`](https://build.alpinelinux.org/buildlogs/build-edge-aarch64/community/waydroid/waydroid-1.4.2-r5.log)) on my FP4 running postmarketOS exhibits the behaviour, as does my CalyxOS Google Pixel 3, and stock FP5. [^1]: [`koji.fedoraproject.org/koji/rpminfo?rpmID=38042996`][1] [1]: https://koji.fedoraproject.org/koji/rpminfo?rpmID=38042996
GiteaMirror commented 2026-05-26 21:18:22 -05:00
Author
Owner
Copy Link
Copy Source

@vvolkgang commented on GitHub (Jun 20, 2024):

Issue migrated to https://github.com/bitwarden/mobile/issues/3207

<!-- gh-comment-id:2181382118 --> @vvolkgang commented on GitHub (Jun 20, 2024): Issue migrated to https://github.com/bitwarden/mobile/issues/3207
GiteaMirror commented 2026-05-26 21:18:25 -05:00
Author
Owner
Copy Link
Copy Source

@RokeJulianLockhart commented on GitHub (Jun 20, 2024):

https://github.com/bitwarden/android/issues/3207#issuecomment-2181382118

@vvolkgang, would have been better to use the GitHub-native migration feature, since I can't edit that issue description and my comments to improve them retroactively.

Thanks, though.

<!-- gh-comment-id:2181396499 --> @RokeJulianLockhart commented on GitHub (Jun 20, 2024): > https://github.com/bitwarden/android/issues/3207#issuecomment-2181382118 @vvolkgang, would have been better to use the GitHub-native migration feature, since I can't edit that issue description and my comments to improve them retroactively. Thanks, though.
GiteaMirror commented 2026-05-26 21:18:26 -05:00
Author
Owner
Copy Link
Copy Source

@RokeJulianLockhart commented on GitHub (Jun 23, 2025):

This remains, per https://github.com/bitwarden/android/issues/5412#issue-3169569962.

<!-- gh-comment-id:2998080794 --> @RokeJulianLockhart commented on GitHub (Jun 23, 2025): This remains, per https://github.com/bitwarden/android/issues/5412#issue-3169569962.
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 labels bug
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
GiteaMirror ninjasurge (Kaehlen Rog)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#88293