2024.11.0 Crash #2046

Closed
opened 2025-11-26 23:06:14 -06:00 by GiteaMirror · 13 comments
Owner

Originally created by @pcartwright81 on GitHub (Nov 2, 2024).

Steps To Reproduce

Open the app. Put finger on scanner. Crash.
Everything was working on the previous version.

Expected Result

Open the app. Put finger on scanner. App unlocks.

Actual Result

Open the app. Put finger on scanner. Crash.
Everything was working on the previous version.

Screenshots or Videos

No response

Additional Context

Clearing cache does not fix the issue, but clearing storage does

Build Version

2024.11.0

What server are you connecting to?

US

Self-host Server Version

No response

Environment Details

Pixel 9 pro XL Android 15

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 @pcartwright81 on GitHub (Nov 2, 2024). ### Steps To Reproduce Open the app. Put finger on scanner. Crash. Everything was working on the previous version. ### Expected Result Open the app. Put finger on scanner. App unlocks. ### Actual Result Open the app. Put finger on scanner. Crash. Everything was working on the previous version. ### Screenshots or Videos _No response_ ### Additional Context Clearing cache does not fix the issue, but clearing storage does ### Build Version 2024.11.0 ### What server are you connecting to? US ### Self-host Server Version _No response_ ### Environment Details Pixel 9 pro XL Android 15 ### 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.
GiteaMirror added the bug label 2025-11-26 23:06:14 -06:00
Author
Owner

@bitwarden-bot commented on GitHub (Nov 2, 2024):

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

@bitwarden-bot commented on GitHub (Nov 2, 2024): Thank you for your report! We've added this to our internal board for review. ID: PM-14433
Author
Owner

@Vstory commented on GitHub (Nov 4, 2024):

Same error, here is the crash log.

Generated by AppErrorsTracking 1.3(6)
Project URL: https://github.com/KitsunePie/AppErrorsTracking
[Device Brand]: Xiaomi
[Device Model]: M2102K1AC
[Display]: TKQ1.220829.002 test-keys
[Android Version]: 13
[Android API Level]: 33
[System Locale]: zh_CN
[Process ID]: 10215
[User ID]: 0
[CPU ABI]: arm64-v8a
[Package Name]: com.x8bit.bitwarden
[Version Name]: 2024.11.0
[Version Code]: 19415
[Target SDK]: 34
[Min SDK]: 29
[Error Type]: JVM
[Crash Time]: 2024-11-04T10:14:03.624
[Stack Trace]:
java.lang.NullPointerException: Attempt to read from field 'java.lang.String P7.c.b' on a null object reference in method 'java.lang.Object J7.o.invokeSuspend(java.lang.Object)'
	at J7.o.invokeSuspend(Unknown Source:11)
	at Gb.a.resumeWith(Unknown Source:7)
	at bc.K.run(Unknown Source:106)
	at ic.b.run(Unknown Source:126)
	Suppressed: kotlinx.coroutines.internal.DiagnosticCoroutineContextException: [s0{Cancelling}@bad453f, Dispatchers.Unconfined]
@Vstory commented on GitHub (Nov 4, 2024): Same error, here is the crash log. ``` Generated by AppErrorsTracking 1.3(6) Project URL: https://github.com/KitsunePie/AppErrorsTracking [Device Brand]: Xiaomi [Device Model]: M2102K1AC [Display]: TKQ1.220829.002 test-keys [Android Version]: 13 [Android API Level]: 33 [System Locale]: zh_CN [Process ID]: 10215 [User ID]: 0 [CPU ABI]: arm64-v8a [Package Name]: com.x8bit.bitwarden [Version Name]: 2024.11.0 [Version Code]: 19415 [Target SDK]: 34 [Min SDK]: 29 [Error Type]: JVM [Crash Time]: 2024-11-04T10:14:03.624 [Stack Trace]: java.lang.NullPointerException: Attempt to read from field 'java.lang.String P7.c.b' on a null object reference in method 'java.lang.Object J7.o.invokeSuspend(java.lang.Object)' at J7.o.invokeSuspend(Unknown Source:11) at Gb.a.resumeWith(Unknown Source:7) at bc.K.run(Unknown Source:106) at ic.b.run(Unknown Source:126) Suppressed: kotlinx.coroutines.internal.DiagnosticCoroutineContextException: [s0{Cancelling}@bad453f, Dispatchers.Unconfined] ```
Author
Owner

@differsthecat commented on GitHub (Nov 4, 2024):

Hi @pcartwright81 , @Vstory, we are actively looking into this and are having a hard time diagnosing what could be the issue. Can you provide more info to help us investigate?

  1. What login/unlock methods are you using? Biometrics?
  2. Do you have 2fa enabled?
  3. Do you have multiple accounts?
  4. What environment are you connecting to? (US cloud, EU cloud, or self-hosted)

If you don't want to share this publicly, you can contact our support team directly here or by emailing support@bitwarden.com.

@differsthecat commented on GitHub (Nov 4, 2024): Hi @pcartwright81 , @Vstory, we are actively looking into this and are having a hard time diagnosing what could be the issue. Can you provide more info to help us investigate? 1. What login/unlock methods are you using? Biometrics? 2. Do you have 2fa enabled? 3. Do you have multiple accounts? 4. What environment are you connecting to? (US cloud, EU cloud, or self-hosted) If you don't want to share this publicly, you can contact our support team directly [here](https://bitwarden.com/contact/) or by emailing support@bitwarden.com.
Author
Owner

@pcartwright81 commented on GitHub (Nov 4, 2024):

1 Biometrics
2 Yes 2FA
3 Only 1 Account, 900+ passwords
4 US Prod

@pcartwright81 commented on GitHub (Nov 4, 2024): 1 Biometrics 2 Yes 2FA 3 Only 1 Account, 900+ passwords 4 US Prod
Author
Owner

@gl-dude commented on GitHub (Nov 5, 2024):

I'm also getting the same crash.

FATAL EXCEPTION: arch_disk_io_0
Process: com.x8bit.bitwarden, PID: 6959
java.lang.NullPointerException: Attempt to read from field 'java.lang.String M7.c.b' on a null object reference in method 'java.lang.Object G7.p.invokeSuspend(java.lang.Object)'
	at G7.p.invokeSuspend(Unknown Source:11)
	at Cb.a.resumeWith(Unknown Source:7)
	at Xb.K.run(Unknown Source:106)
	at ec.b.run(Unknown Source:126)
	Suppressed: kotlinx.coroutines.internal.DiagnosticCoroutineContextException: [s0{Cancelling}@6602311, Dispatchers.Unconfined]

Bitwarden version: 2024.11.0 (19421)
Android version: 14 (LineageOS)

It seems to occur if I've rebooted my phone and then don't use Bitwarden at all for a while. Then when I click on "Go to my vault" and it prompts me for my fingerprint, it crashes. But if I then open Bitwarden from my launcher the crashes will stop for a while and I can select logins.

In comparison, 2024.9.0-beta (19209) was flawless for me.

@gl-dude commented on GitHub (Nov 5, 2024): I'm also getting the same crash. ``` FATAL EXCEPTION: arch_disk_io_0 Process: com.x8bit.bitwarden, PID: 6959 java.lang.NullPointerException: Attempt to read from field 'java.lang.String M7.c.b' on a null object reference in method 'java.lang.Object G7.p.invokeSuspend(java.lang.Object)' at G7.p.invokeSuspend(Unknown Source:11) at Cb.a.resumeWith(Unknown Source:7) at Xb.K.run(Unknown Source:106) at ec.b.run(Unknown Source:126) Suppressed: kotlinx.coroutines.internal.DiagnosticCoroutineContextException: [s0{Cancelling}@6602311, Dispatchers.Unconfined] ``` Bitwarden version: 2024.11.0 (19421) Android version: 14 (LineageOS) It seems to occur if I've rebooted my phone and then don't use Bitwarden at all for a while. Then when I click on "Go to my vault" and it prompts me for my fingerprint, it crashes. But if I then open Bitwarden from my launcher the crashes will stop for a while and I can select logins. In comparison, 2024.9.0-beta (19209) was flawless for me.
Author
Owner

@Vstory commented on GitHub (Nov 5, 2024):

Same error, here is the crash log.

Generated by AppErrorsTracking 1.3(6)
Project URL: https://github.com/KitsunePie/AppErrorsTracking
[Device Brand]: Xiaomi
[Device Model]: M2102K1AC
[Display]: TKQ1.220829.002 test-keys
[Android Version]: 13
[Android API Level]: 33
[System Locale]: zh_CN
[Process ID]: 10215
[User ID]: 0
[CPU ABI]: arm64-v8a
[Package Name]: com.x8bit.bitwarden
[Version Name]: 2024.11.0
[Version Code]: 19415
[Target SDK]: 34
[Min SDK]: 29
[Error Type]: JVM
[Crash Time]: 2024-11-04T10:14:03.624
[Stack Trace]:
java.lang.NullPointerException: Attempt to read from field 'java.lang.String P7.c.b' on a null object reference in method 'java.lang.Object J7.o.invokeSuspend(java.lang.Object)'
	at J7.o.invokeSuspend(Unknown Source:11)
	at Gb.a.resumeWith(Unknown Source:7)
	at bc.K.run(Unknown Source:106)
	at ic.b.run(Unknown Source:126)
	Suppressed: kotlinx.coroutines.internal.DiagnosticCoroutineContextException: [s0{Cancelling}@bad453f, Dispatchers.Unconfined]

When using autofill, the app crashes after jumping to unlock the vault and verifying the fingerprint.

@Vstory commented on GitHub (Nov 5, 2024): > Same error, here is the crash log. > > ``` > Generated by AppErrorsTracking 1.3(6) > Project URL: https://github.com/KitsunePie/AppErrorsTracking > [Device Brand]: Xiaomi > [Device Model]: M2102K1AC > [Display]: TKQ1.220829.002 test-keys > [Android Version]: 13 > [Android API Level]: 33 > [System Locale]: zh_CN > [Process ID]: 10215 > [User ID]: 0 > [CPU ABI]: arm64-v8a > [Package Name]: com.x8bit.bitwarden > [Version Name]: 2024.11.0 > [Version Code]: 19415 > [Target SDK]: 34 > [Min SDK]: 29 > [Error Type]: JVM > [Crash Time]: 2024-11-04T10:14:03.624 > [Stack Trace]: > java.lang.NullPointerException: Attempt to read from field 'java.lang.String P7.c.b' on a null object reference in method 'java.lang.Object J7.o.invokeSuspend(java.lang.Object)' > at J7.o.invokeSuspend(Unknown Source:11) > at Gb.a.resumeWith(Unknown Source:7) > at bc.K.run(Unknown Source:106) > at ic.b.run(Unknown Source:126) > Suppressed: kotlinx.coroutines.internal.DiagnosticCoroutineContextException: [s0{Cancelling}@bad453f, Dispatchers.Unconfined] > ``` When using autofill, the app crashes after jumping to unlock the vault and verifying the fingerprint.
Author
Owner

@Vstory commented on GitHub (Nov 5, 2024):

  1. What login/unlock methods are you using? Biometrics?

Yes

  1. Do you have 2fa enabled?

No

  1. Do you have multiple accounts?

900+

  1. What environment are you connecting to? (US cloud, EU cloud, or self-hosted)

Us Cloud

@Vstory commented on GitHub (Nov 5, 2024): > 1. What login/unlock methods are you using? Biometrics? Yes > 2. Do you have 2fa enabled? No > 3. Do you have multiple accounts? 900+ > 4. What environment are you connecting to? (US cloud, EU cloud, or self-hosted) Us Cloud
Author
Owner

@differsthecat commented on GitHub (Nov 6, 2024):

Thank you all for the info; it has been very helpful!

We believe we have fixed this with #4231, which has been released in version 2024.11.1.

@differsthecat commented on GitHub (Nov 6, 2024): Thank you all for the info; it has been very helpful! We believe we have fixed this with #4231, which has been released in version `2024.11.1`.
Author
Owner

@gl-dude commented on GitHub (Nov 8, 2024):

@differsthecat @dseverns-livefront

I'm currently using 2024.11.3 (19432) and it did indeed fix the crash, but now it's masking the issue, because now it just loads the "Items for github.com" screen, but it doesn't list any of my accounts. So to work around that issue, I need to back out of that screen and load up Bitwarden from my launcher. And only then will it start showing the accounts that I can use.

As I said in my previous post, 2024.9.0-beta (19209) worked perfectly in comparison.

@gl-dude commented on GitHub (Nov 8, 2024): @differsthecat @dseverns-livefront I'm currently using 2024.11.3 (19432) and it did indeed fix the crash, but now it's masking the issue, because now it just loads the "Items for github.com" screen, but it doesn't list any of my accounts. So to work around that issue, I need to back out of that screen and load up Bitwarden from my launcher. And only then will it start showing the accounts that I can use. As I said in my previous post, 2024.9.0-beta (19209) worked perfectly in comparison.
Author
Owner

@pcartwright81 commented on GitHub (Nov 8, 2024):

Thanks, I was wondering if this was only a me issue. Although swiping down from the top and it loading the items is much less annoying than the bug that was closed.

@pcartwright81 commented on GitHub (Nov 8, 2024): Thanks, I was wondering if this was only a me issue. Although swiping down from the top and it loading the items is much less annoying than the bug that was closed.
Author
Owner

@gl-dude commented on GitHub (Nov 9, 2024):

If I could find a consistent way to reproduce the issue, I'd just compile the app myself and roll back changes until I find the exact one that triggers the bug.

But it seems like if your phone becomes low on memory (play a game or use Firefox with 50+ tabs) and closes some background processes, then selecting "Go to my vault" can result in Bitwarden displaying the "Items for ..." screen without first loading in the database. But this has only been an issue since they changed the UI for the "stable" release.

@gl-dude commented on GitHub (Nov 9, 2024): If I could find a consistent way to reproduce the issue, I'd just compile the app myself and roll back changes until I find the exact one that triggers the bug. But it seems like if your phone becomes low on memory (play a game or use Firefox with 50+ tabs) and closes some background processes, then selecting "Go to my vault" can result in Bitwarden displaying the "Items for ..." screen without first loading in the database. But this has only been an issue since they changed the UI for the "stable" release.
Author
Owner

@pcartwright81 commented on GitHub (Nov 9, 2024):

This version is a complete rewrite from C# to a native Kotlin app. A bug fix for infinite loading was pushed yesterday and I thought I was commenting on that one. I can't remember getting no items before yesterday.

@pcartwright81 commented on GitHub (Nov 9, 2024): This version is a complete rewrite from C# to a native Kotlin app. A bug fix for infinite loading was pushed yesterday and I thought I was commenting on that one. I can't remember getting no items before yesterday.
Author
Owner

@gl-dude commented on GitHub (Nov 9, 2024):

This version is a complete rewrite from C# to a native Kotlin app

What I meant was that going from the native beta version to the native stable version is what introduced this bug, since they changed the UI even more for the stable release.

Maybe you could try the earlier beta version to see if that works correctly for you too?

I actually started using Bitwarden just as they released this native version on GitHub. And I'm glad they did, since I really didn't like the original C# version.

@gl-dude commented on GitHub (Nov 9, 2024): > This version is a complete rewrite from C# to a native Kotlin app What I meant was that going from the [native beta version](https://github.com/bitwarden/android/releases/tag/v2024.9.0) to the [native stable version](https://github.com/bitwarden/android/releases/tag/v2024.10.1) is what introduced this bug, since they changed the UI even more for the stable release. Maybe you could try the earlier beta version to see if that works correctly for you too? I actually started using Bitwarden just as they released this native version on GitHub. And I'm glad they did, since I really didn't like the original C# version.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#2046