github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-03-22 12:32:53 -05:00
Code Issues 144 Packages Projects Releases 118 Wiki Activity

[Android] Force close after updating to 1.6.0 #59

New Issue
Closed
opened 2025-11-07 08:24:56 -06:00 by GiteaMirror · 9 comments
GiteaMirror commented 2025-11-07 08:24:56 -06:00
Owner
Copy Link

Originally created by @walrus543 on GitHub (Jun 7, 2017).

Hi,
I have just updated to the version 1.6.0 from the Play Store and I have a force close when I try to open the app. (I didn't have this issue with the testing apk)

Here is the log:
Log_2017-06-07_08-31-08.txt

Originally created by @walrus543 on GitHub (Jun 7, 2017). Hi, I have just updated to the version 1.6.0 from the Play Store and I have a force close when I try to open the app. (I didn't have this issue with the testing apk) Here is the log: [Log_2017-06-07_08-31-08.txt](https://github.com/bitwarden/mobile/files/1057079/Log_2017-06-07_08-31-08.txt)
GiteaMirror commented 2025-11-07 08:24:57 -06:00
Author
Owner
Copy Link

@jerryn70 commented on GitHub (Jun 7, 2017):

Maybe the test apk and play store apk do not match. What about fresh install ?

Still i didn't received 1.6.0 version on my play store and there is no 1.6.0 apk release in github.

@jerryn70 commented on GitHub (Jun 7, 2017): Maybe the test apk and play store apk do not match. What about fresh install ? Still i didn't received 1.6.0 version on my play store and there is no 1.6.0 apk release in github.
GiteaMirror commented 2025-11-07 08:24:57 -06:00
Author
Owner
Copy Link

@ple103 commented on GitHub (Jun 7, 2017):

@jerryn70 Same here. The latest version for me is 1.5.1 on the Play Store. I think Primo may be on the beta program.
Test APKs are released here: https://ci.appveyor.com/project/bitwarden/mobile/history.

@ple103 commented on GitHub (Jun 7, 2017): @jerryn70 Same here. The latest version for me is 1.5.1 on the Play Store. I think Primo may be on the beta program. Test APKs are released here: https://ci.appveyor.com/project/bitwarden/mobile/history.
GiteaMirror commented 2025-11-07 08:24:57 -06:00
Author
Owner
Copy Link

@jerryn70 commented on GitHub (Jun 7, 2017):

@ple103 i know about the test apk.
I mean there is no 1.6.0 version in this page
https://github.com/bitwarden/mobile/releases

@jerryn70 commented on GitHub (Jun 7, 2017): @ple103 i know about the test apk. I mean there is no 1.6.0 version in this page https://github.com/bitwarden/mobile/releases
GiteaMirror commented 2025-11-07 08:24:58 -06:00
Author
Owner
Copy Link

@walrus543 commented on GitHub (Jun 7, 2017):

Yes, I'm on the beta program and I was talking about the testing apk v802.

I cleared app data then uninstalled it. So I have now a fresh installation.
I no longer have the force but I don't get any notification... The Accessibility service is enabled (btw we could have a request to enable it when launching the app for the first time).
idk what could be the problem...

EDIT: fixed after a reboot o_O

@jerryn70 Could you please try the 1.6.0 version and let me know if you also have a FC?

@walrus543 commented on GitHub (Jun 7, 2017): Yes, I'm on the beta program and I was talking about the testing apk [v802](https://github.com/bitwarden/mobile/issues/69). I cleared app data then uninstalled it. So I have now a fresh installation. I no longer have the force but I don't get any notification... The Accessibility service is enabled (btw we could have a request to enable it when launching the app for the first time). idk what could be the problem... EDIT: fixed after a reboot o_O @jerryn70 Could you please try the 1.6.0 version and let me know if you also have a FC?
GiteaMirror commented 2025-11-07 08:24:58 -06:00
Author
Owner
Copy Link

@jerryn70 commented on GitHub (Jun 7, 2017):

@Primokorn you mean fresh install from play store ? Or update from old version?

If it is update, then i can't do that because I'm currently running on test version 798 and in play store no update is showing.

To test 1.6.0 i need to uninstall v798 i think.

@jerryn70 commented on GitHub (Jun 7, 2017): @Primokorn you mean fresh install from play store ? Or update from old version? If it is update, then i can't do that because I'm currently running on test version 798 and in play store no update is showing. To test 1.6.0 i need to uninstall v798 i think.
GiteaMirror commented 2025-11-07 08:24:58 -06:00
Author
Owner
Copy Link

@jerryn70 commented on GitHub (Jun 7, 2017):

@Primokorn Joined bitwarden beta.
Installed test version 802 then updated to 1.6.0 beta from play store . And got FC.

Tried fresh install of 1.6.0 And done all proper settings, but auto fill is not showing. Accessibility is ON but in bitwarden the status is disabled.

@jerryn70 commented on GitHub (Jun 7, 2017): @Primokorn Joined bitwarden beta. Installed test version 802 then updated to 1.6.0 beta from play store . And got FC. Tried fresh install of 1.6.0 And done all proper settings, but auto fill is not showing. Accessibility is ON but in bitwarden the status is disabled. ![](http://i.imgur.com/Ml8MXOy.png)
GiteaMirror commented 2025-11-07 08:24:59 -06:00
Author
Owner
Copy Link

@kspearrin commented on GitHub (Jun 7, 2017):

This should now be resolved in the beta with build 824. If you can, please help test the following scenario:

  1. Uninstall bitwarden completely.
  2. Leave beta program.
  3. Install non-beta version (v1.5.1)
  4. Log in and activate fingerprint or other lock option.
  5. Join beta program.
  6. Update to 1.6.0 beta (824)
  7. Confirm that you did not get logged out and no crashes are happening.
  8. Edit and/or add a login.
@kspearrin commented on GitHub (Jun 7, 2017): This should now be resolved in the beta with build 824. If you can, please help test the following scenario: 1. Uninstall bitwarden completely. 2. Leave beta program. 3. Install non-beta version (v1.5.1) 4. Log in and activate fingerprint or other lock option. 5. Join beta program. 6. Update to 1.6.0 beta (824) 7. Confirm that you did not get logged out and no crashes are happening. 8. Edit and/or add a login.
GiteaMirror commented 2025-11-07 08:24:59 -06:00
Author
Owner
Copy Link

@walrus543 commented on GitHub (Jun 7, 2017):

Everything is working flawlessly.
It was a problem due to the testing version?

@walrus543 commented on GitHub (Jun 7, 2017): Everything is working flawlessly. It was a problem due to the testing version?
GiteaMirror commented 2025-11-07 08:24:59 -06:00
Author
Owner
Copy Link

@kspearrin commented on GitHub (Jun 7, 2017):

@Primokorn Yes, there was a bug in the last beta build. @ple103 and I fixed it last night.

@kspearrin commented on GitHub (Jun 7, 2017): @Primokorn Yes, there was a bug in the last beta build. @ple103 and I fixed it last night.
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#59
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?