F-Droid App crashes when generating new password for new app login #1532

Closed
opened 2025-11-26 22:51:53 -06:00 by GiteaMirror · 3 comments
Owner

Originally created by @TheDoctorT on GitHub (Nov 21, 2022).

Steps To Reproduce

  1. Open an app that necessitates a login
  2. Go to the login page and open the BitWarden Vault by tapping on the prompt
  3. Tap the plus icon to create a new login
  4. Tap on the circling arrows next to the password field to generate a new password

Expected Result

The password generator should open and generate a new password.

Actual Result

The application crashes.

Screenshots or Videos

No response

Additional Context

The application is the F-Droid version. Additionally, this only happens if the new login is for an application, whereas the same process behaves fine when creating a new browser login.

I tested it on 2 different applications: org.telegram.messenger and com.lgi.upcch
A third application, ch.ethz.eduapp, did not show this behaviour.

This phone has Android One installed.

Operating System

Android

Operating System Version

Android 10

Device

HTC U11 Life

Build Version

2022.10.0 (5247)

Beta

  • Using a pre-release version of the application.
Originally created by @TheDoctorT on GitHub (Nov 21, 2022). ### Steps To Reproduce 1. Open an app that necessitates a login 2. Go to the login page and open the BitWarden Vault by tapping on the prompt 3. Tap the plus icon to create a new login 4. Tap on the circling arrows next to the password field to generate a new password ### Expected Result The password generator should open and generate a new password. ### Actual Result The application crashes. ### Screenshots or Videos _No response_ ### Additional Context The application is the F-Droid version. Additionally, this only happens if the new login is for an application, whereas the same process behaves fine when creating a new browser login. I tested it on 2 different applications: org.telegram.messenger and com.lgi.upcch A third application, ch.ethz.eduapp, did not show this behaviour. This phone has Android One installed. ### Operating System Android ### Operating System Version Android 10 ### Device HTC U11 Life ### Build Version 2022.10.0 (5247) ### Beta - [ ] Using a pre-release version of the application.
GiteaMirror added the bug label 2025-11-26 22:51:53 -06:00
Author
Owner

@TheDoctorT commented on GitHub (Nov 21, 2022):

I tested it some more and found some nuances:

  1. If I reboot the phone and follow the steps it crashes as described.
  2. If I reboot the phone, follow until step 2, autofill with another login item, reopen the app from the prompt in the login screen and follow steps 3-4 it crashes.
  3. If I reboot the phone, open the app, unlock the vault, lock the vault and then follow the steps, it doesn't crash. It doesn't crash even if the vault remains open.
  4. If I reboot the phone, open the app, unlock the vault, remove the app from multitasking ("swipe up") and then follow the steps, it crashes.

This behaviour appears in the applications already described as well as ch.protonmail.android and even ch.ethz.eduapp, contrary to what previously stated.

It seems like it has to do with the app already running, but not quite, because following procedure 2 the vault remains open the second time, and the app opens a instantly, showing that it is already running. S it differentiates between being opened from a password prompt and being opened directly?

@TheDoctorT commented on GitHub (Nov 21, 2022): I tested it some more and found some nuances: 1. If I reboot the phone and follow the steps it crashes as described. 2. If I reboot the phone, follow until step 2, autofill with another login item, reopen the app from the prompt in the login screen and follow steps 3-4 it crashes. 3. If I reboot the phone, open the app, unlock the vault, lock the vault and then follow the steps, it doesn't crash. It doesn't crash even if the vault remains open. 4. If I reboot the phone, open the app, unlock the vault, remove the app from multitasking ("swipe up") and then follow the steps, it crashes. This behaviour appears in the applications already described as well as ch.protonmail.android and even ch.ethz.eduapp, contrary to what previously stated. It seems like it has to do with the app already running, but not quite, because following procedure 2 the vault remains open the second time, and the app opens a instantly, showing that it is already running. S it differentiates between being opened from a password prompt and being opened directly?
Author
Owner

@djsmith85 commented on GitHub (Nov 21, 2022):

Hi @TheDoctorT and thank you for your report.

This seems to be a duplicate of https://github.com/bitwarden/mobile/issues/2149, which has already received a fix.

This should be resolved with the next release (2022.11)

Closing this now.

@djsmith85 commented on GitHub (Nov 21, 2022): Hi @TheDoctorT and thank you for your report. This seems to be a duplicate of https://github.com/bitwarden/mobile/issues/2149, which has already received a fix. This should be resolved with the next release (2022.11) Closing this now.
Author
Owner

@TheDoctorT commented on GitHub (Nov 21, 2022):

Yes, seems like it. I looked for reports but only under "Open", and didn't see this one. Sorry for wasting your time.

@TheDoctorT commented on GitHub (Nov 21, 2022): Yes, seems like it. I looked for reports but only under "Open", and didn't see this one. Sorry for wasting your time.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#1532