github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-05-08 04:16:40 -05:00
Code Issues 1.1k Packages Projects Releases 122 Wiki Activity

[GH-ISSUE #1212] [Android] - App Crashes After Attempting Unlock With Password #7204

New Issue
Closed
opened 2026-04-10 23:39:00 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-04-10 23:39:00 -05:00
Owner
Copy Link

Originally created by @nezartarbin on GitHub (Jan 7, 2021).
Original GitHub issue: https://github.com/bitwarden/android/issues/1212

Describe the Bug

Hi! I am having an issue where, when I open my app, I attempt to login / unlock by entering my password. As soon as I hit "unlock" (after I fill in my password) the screen immediately goes back to home screen, indicating that the app crashed. Subsequent attempts have the same result.

Steps To Reproduce

  1. Launch the app
  2. Fill in password
  3. Hit "unlock" button

Expected Result

The vault is unlocked and launched correctly.

Actual Result

the app seems to crash, because screen goes back to home immediately.

Screenshots or Videos

Environment

  • Device: OnePlus 8T
  • Operating system: Android 11
  • Build Version: 11.0.5.7.KB09CB
  • Is this a Beta release? No

Additional Context

I am self-hosting Bitwarden. It works without issues on the web app, and it used to work on the mobile app too.

Whenever I attempt to delete the app and reinstall, the first login is successful and I can unlock the vault without issue. It is only after the first login that the issue starts to happen. But every time I uninstall and reinstall, it works for one login.

Upon further investigation, I found out that, instead of filling in the password, if I log out (by choosing the option from the top right menu) then log back in (with both email and password), it works without issue. But if I don't explicitly log out to log back in, and simply unlock the vault, it crashes.

I tried both the F-droid and the Google Play store versions.

Help me please, and thank you for this amazing software :)

Originally created by @nezartarbin on GitHub (Jan 7, 2021). Original GitHub issue: https://github.com/bitwarden/android/issues/1212 <!-- Comment: Please do not submit feature requests. The [Community Forums][1] has a section for submitting, voting for, and discussing product feature requests. [1]: https://community.bitwarden.com --> ## Describe the Bug Hi! I am having an issue where, when I open my app, I attempt to login / unlock by entering my password. As soon as I hit "unlock" (after I fill in my password) the screen immediately goes back to home screen, indicating that the app crashed. Subsequent attempts have the same result. <!-- Comment: A clear and concise description of what the bug is. --> ## Steps To Reproduce 1. Launch the app 2. Fill in password 3. Hit "unlock" button <!-- Comment: How can we reproduce the behavior: --> ## Expected Result The vault is unlocked and launched correctly. <!-- Comment: A clear and concise description of what you expected to happen. --> ## Actual Result the app seems to crash, because screen goes back to home immediately. <!-- Comment: A clear and concise description of what is happening. --> ## Screenshots or Videos <!-- Comment: If applicable, add screenshots and/or a short video to help explain your problem. --> ## Environment - Device: OnePlus 8T - Operating system: Android 11 - Build Version: 11.0.5.7.KB09CB - Is this a Beta release? No ## Additional Context I am self-hosting Bitwarden. It works without issues on the web app, and it used to work on the mobile app too. Whenever I attempt to delete the app and reinstall, the first login is successful and I can unlock the vault without issue. It is only after the first login that the issue starts to happen. But every time I uninstall and reinstall, it works for one login. Upon further investigation, I found out that, instead of filling in the password, if I log out (by choosing the option from the top right menu) then log back in (with both email and password), it works without issue. But if I don't explicitly log out to log back in, and simply unlock the vault, it crashes. I tried both the F-droid and the Google Play store versions. Help me please, and thank you for this amazing software :) <!-- Comment: Add any other context about the problem here. -->
GiteaMirror commented 2026-04-10 23:39:02 -05:00
Author
Owner
Copy Link

@mpbw2 commented on GitHub (Jan 8, 2021):

What version of the app are you using, and are you using the latest docker images?

<!-- gh-comment-id:756811872 --> @mpbw2 commented on GitHub (Jan 8, 2021): What version of the app are you using, and are you using the latest docker images?
GiteaMirror commented 2026-04-10 23:39:03 -05:00
Author
Owner
Copy Link

@zucki commented on GitHub (Jan 20, 2021):

I have the same problem.
I'm using:
Samsung Galaxy S8 with Android 9
Bitwarden Mobile App version 2.7.0 from F-Droid and Bitwarden repo
latest bitwardenrs docker with Bitwarden Version 2.16.1

<!-- gh-comment-id:763480581 --> @zucki commented on GitHub (Jan 20, 2021): I have the same problem. I'm using: Samsung Galaxy S8 with Android 9 Bitwarden Mobile App version 2.7.0 from F-Droid and Bitwarden repo latest bitwardenrs docker with Bitwarden Version 2.16.1
GiteaMirror commented 2026-04-10 23:39:04 -05:00
Author
Owner
Copy Link

@nezartarbin commented on GitHub (Oct 28, 2022):

I no longer have this issue, so I am closing.

<!-- gh-comment-id:1295257571 --> @nezartarbin commented on GitHub (Oct 28, 2022): I no longer have this issue, so I am closing.
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
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#7204
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?