Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug v1.10.1: App crash after activation of fingerprint. #1391

Closed
Malixxa opened this issue Jul 19, 2023 · 6 comments
Closed

Bug v1.10.1: App crash after activation of fingerprint. #1391

Malixxa opened this issue Jul 19, 2023 · 6 comments
Assignees

Comments

@Malixxa
Copy link
Collaborator

Malixxa commented Jul 19, 2023

No description provided.

@Malixxa Malixxa changed the title Bug v1.10.0: App crash after activation of fingerprint. Bug v1.10.1: App crash after activation of fingerprint. Jul 19, 2023
@clangenb
Copy link
Member

This is not good at all. It will be difficult to debug, I could not reproduce it so far. The question is, maybe we should revert #1361. Which would mean that the app asks again for enabling biometrics after a subsequent update (which we actually considered a bug).

@Malixxa
Copy link
Collaborator Author

Malixxa commented Jul 19, 2023

I think the person has still v1.10.1. So not the updated version via TestFlight / Android Beta, which means the biometrics implementation causes the bug. @brenzi can get more infos. With my current knowledge I would try to publish the update asap and see if it still crashes.

@clangenb
Copy link
Member

Hard to debug, as we don't have diagnostics. Plan for now:

  • Search biometrics code if exceptions can be thrown.
  • if yes, catch them and disable biometrics again. And show dialog to user.

1 similar comment
@clangenb
Copy link
Member

Hard to debug, as we don't have diagnostics. Plan for now:

  • Search biometrics code if exceptions can be thrown.
  • if yes, catch them and disable biometrics again. And show dialog to user.

@brenzi
Copy link
Member

brenzi commented Aug 10, 2023

The update 1.10.4 has recovered this user's app. must have been a very weird edge case. no chance to investigate, unfortunately

@brenzi brenzi closed this as completed Aug 10, 2023
@Malixxa
Copy link
Collaborator Author

Malixxa commented Aug 10, 2023

Nice!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants