github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-03-19 13:36:39 -05:00
Code Issues 144 Packages Projects Releases 116 Wiki Activity

iOS 13.0 Application Crash #834

New Issue
Closed
opened 2025-11-26 22:31:59 -06:00 by GiteaMirror · 12 comments
GiteaMirror commented 2025-11-26 22:31:59 -06:00
Owner
Copy Link

Originally created by @TwoTenPvP on GitHub (Sep 27, 2019).

I previously used an iPhone XS Max on iOS 12.1.1 Beta 1. I bought an iPhone 11 Pro Max and restored using iCloud. Since then, Bitwarden crashes just a few seconds after it's started. I can still interact with the app in that time, like accessing settings. Must be a fetch crash.

Unable to get any stacktraces as I don't own a macintosh.

Video here

Note that this is on version 2.2.3 with the iOS 13 fixes.

Originally created by @TwoTenPvP on GitHub (Sep 27, 2019). <!-- 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 --> I previously used an iPhone XS Max on iOS 12.1.1 Beta 1. I bought an iPhone 11 Pro Max and restored using iCloud. Since then, Bitwarden crashes just a few seconds after it's started. I can still interact with the app in that time, like accessing settings. Must be a fetch crash. Unable to get any stacktraces as I don't own a macintosh. [Video here](https://youtu.be/4BJ-GbvGsIM) Note that this is on version 2.2.3 with the iOS 13 fixes.
GiteaMirror commented 2025-11-26 22:31:59 -06:00
Author
Owner
Copy Link

@TwoTenPvP commented on GitHub (Sep 27, 2019):

Issue also present on iOS 13.1.1, guessing that isn't too helpful but might aswell let you know.

@TwoTenPvP commented on GitHub (Sep 27, 2019): Issue also present on iOS 13.1.1, guessing that isn't too helpful but might aswell let you know.
GiteaMirror commented 2025-11-26 22:32:00 -06:00
Author
Owner
Copy Link

@TwoTenPvP commented on GitHub (Sep 27, 2019):

Issue fixed when manually logging out of account, then logging back in. Should probably still be looked into even if the reproduction involves restoration.

@TwoTenPvP commented on GitHub (Sep 27, 2019): Issue fixed when manually logging out of account, then logging back in. Should probably still be looked into even if the reproduction involves restoration.
GiteaMirror commented 2025-11-26 22:32:00 -06:00
Author
Owner
Copy Link

@eakoning commented on GitHub (Sep 27, 2019):

@TwoTenPvP this makes two of us. ;-) I was unable to press logout button in the app because Face ID was too fast. I uninstalled and reinstalled the app. Then I could login and it was all and well again...

@eakoning commented on GitHub (Sep 27, 2019): @TwoTenPvP this makes two of us. ;-) I was unable to press logout button in the app because Face ID was too fast. I uninstalled and reinstalled the app. Then I could login and it was all and well again...
GiteaMirror commented 2025-11-26 22:32:00 -06:00
Author
Owner
Copy Link

@TwoTenPvP commented on GitHub (Sep 27, 2019):

@TwoTenPvP this makes two of us. ;-) I was unable to press logout button in the app because Face ID was too fast. I uninstalled and reinstalled the app. Then I could login and it was all and well again...

Yea, I just pointed the phone away from my face.

@TwoTenPvP commented on GitHub (Sep 27, 2019): > @TwoTenPvP this makes two of us. ;-) I was unable to press logout button in the app because Face ID was too fast. I uninstalled and reinstalled the app. Then I could login and it was all and well again... Yea, I just pointed the phone away from my face.
GiteaMirror commented 2025-11-26 22:32:00 -06:00
Author
Owner
Copy Link

@trparky commented on GitHub (Oct 2, 2019):

I'm not the developer but you can access app crash data through the Settings app on your iPhone. Simply open up Settings, Privacy, Analytics, Analytics Data. The only bad part is that you're going to have to sift through all of that stuff in that list to find the app crash data file. Once you find it you can then use the Share sheet to copy the data to the iOS clipboard.

Also, if you sync your device to iTunes on a Windows system you can find the diagnostic logs that are copied from the iOS Device. You can find this data in %appdata%\Apple Computer\Logs\CrashReporter\MobileDevice and then open the folder that's named the same name as your iPhone is named. Then find the log file that pertains to the app that's crashing.

@trparky commented on GitHub (Oct 2, 2019): I'm not the developer but you can access app crash data through the Settings app on your iPhone. Simply open up Settings, Privacy, Analytics, Analytics Data. The only bad part is that you're going to have to sift through all of that stuff in that list to find the app crash data file. Once you find it you can then use the Share sheet to copy the data to the iOS clipboard. Also, if you sync your device to iTunes on a Windows system you can find the diagnostic logs that are copied from the iOS Device. You can find this data in %appdata%\Apple Computer\Logs\CrashReporter\MobileDevice and then open the folder that's named the same name as your iPhone is named. Then find the log file that pertains to the app that's crashing.
GiteaMirror commented 2025-11-26 22:32:01 -06:00
Author
Owner
Copy Link

@maxwowpow commented on GitHub (Nov 15, 2019):

There are some device binding keys (bound to face/touch id) as in virtually all apps.. gmail/instagram etc. after restoring from a backup those apps recognize mismatches and log the user out automatically.

@maxwowpow commented on GitHub (Nov 15, 2019): There are some device binding keys (bound to face/touch id) as in virtually all apps.. gmail/instagram etc. after restoring from a backup those apps recognize mismatches and log the user out automatically.
GiteaMirror commented 2025-11-26 22:32:01 -06:00
Author
Owner
Copy Link

@alexjhart commented on GitHub (Jan 2, 2020):

I've also run into this on a restore/migration.

@alexjhart commented on GitHub (Jan 2, 2020): I've also run into this on a restore/migration.
GiteaMirror commented 2025-11-26 22:32:01 -06:00
Author
Owner
Copy Link

@janharms commented on GitHub (Jun 21, 2020):

I have the same issue on 2.4.3 (69). It is the result of a double entry.
I had an entry for Berliner Sparkasse (Banking Site) which for some reason does not work in the app. (It does not prefill.) I created the same entry again; so I had the same entry twice. This resulted in the app crashing after login with face-Id.
I deleted the entry via the desktop app, logged out of the app and upon login the issue had disappeared.
Regards

@janharms commented on GitHub (Jun 21, 2020): I have the same issue on 2.4.3 (69). It is the result of a double entry. I had an entry for Berliner Sparkasse (Banking Site) which for some reason does not work in the app. (It does not prefill.) I created the same entry again; so I had the same entry twice. This resulted in the app crashing after login with face-Id. I deleted the entry via the desktop app, logged out of the app and upon login the issue had disappeared. Regards
GiteaMirror commented 2025-11-26 22:32:01 -06:00
Author
Owner
Copy Link

@cscharf commented on GitHub (Jun 22, 2020):

@janharms , that doesn't necessarily make sense given items in your vault are not indexed or managed by name/URL, etc. by rather by a globally unique identifier; I would assume it was the act of logging out and back in that "resolved" the issue for you. Can you confirm by re-adding that duplicate and trying again?

If anyone can reproduce and provide app crash logs from their device that would be immensely helpful.

@cscharf commented on GitHub (Jun 22, 2020): @janharms , that doesn't necessarily make sense given items in your vault are not indexed or managed by name/URL, etc. by rather by a globally unique identifier; I would assume it was the act of logging out and back in that "resolved" the issue for you. Can you confirm by re-adding that duplicate and trying again? If anyone can reproduce and provide app crash logs from their device that would be immensely helpful.
GiteaMirror commented 2025-11-26 22:32:02 -06:00
Author
Owner
Copy Link

@janharms commented on GitHub (Jun 22, 2020):

You are right. I cannot reproduce the issue that way anymore. App starts happily even with a duplicate entry.
Must have been a coincidence.

@janharms commented on GitHub (Jun 22, 2020): You are right. I cannot reproduce the issue that way anymore. App starts happily even with a duplicate entry. Must have been a coincidence.
GiteaMirror commented 2025-11-26 22:32:02 -06:00
Author
Owner
Copy Link

@rggjan commented on GitHub (Jul 31, 2020):

Just had the same issue. Video attached (in the zip file) as well as two crashlogs. Logging (by pointing it away from the face, then pressing log out) and in again (with the password + yubikey) still crashes. Reinstalling the app made it work again.

RPReplay_Final1596202762.MP4.zip
crashlogs.zip

@rggjan commented on GitHub (Jul 31, 2020): Just had the same issue. Video attached (in the zip file) as well as two crashlogs. Logging (by pointing it away from the face, then pressing log out) and in again (with the password + yubikey) still crashes. Reinstalling the app made it work again. [RPReplay_Final1596202762.MP4.zip](https://github.com/bitwarden/mobile/files/5007289/RPReplay_Final1596202762.MP4.zip) [crashlogs.zip](https://github.com/bitwarden/mobile/files/5007294/crashlogs.zip)
GiteaMirror commented 2025-11-26 22:32:02 -06:00
Author
Owner
Copy Link

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

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

@vvolkgang commented on GitHub (Jun 20, 2024): Issue migrated to https://github.com/bitwarden/mobile/issues/611
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#834
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?