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

Unlocking a moved vault with biometric auth hangs #524

Open
2 tasks done
XenonSup opened this issue Mar 14, 2024 · 0 comments
Open
2 tasks done

Unlocking a moved vault with biometric auth hangs #524

XenonSup opened this issue Mar 14, 2024 · 0 comments
Labels
type:bug Something isn't working

Comments

@XenonSup
Copy link

Please agree to the following

Summary

Attempting to unlock a vault that's been moved or renamed with biometric authentication enabled blocks the "Vault not found" dialog and enters an infinite loading loop

System Setup

- Android: 14
- Cryptomator: 1.10.0 (Cryptomator F-Droid Repo)

Cloud Type

Dropbox

Steps to Reproduce

  1. Create a new vault on any platform
  2. Add that vault to Android app
  3. Enable biometric unlock for the vault
  4. Move or rename the vault externally
  5. Lock the vault and close Android app
  6. Relaunch cryptomator and tap to open vault

Expected Behavior

I expect the "Vault is not found" dialog to be the only thing displayed.

Actual Behavior

The "Vault is not found" dialog is blocked by the biometric unlock (fingerprint) prompt. This is one bug.

If you move forward with the biometric unlock, the app enters an infinite loading dialog "Please wait..." that is overlaid on top of the vault not found dialog. Nothing works in the app anymore and I have to kill the app to restore functionality.
This might constitute another bug.

If you tap away from from the fingerprint unlock dialog, the app switches to password entry, from which you either tap away or enter any password and it will also result in an infinite loading loop, but you can cancel this one and continue using the app.

Reproducibility

Always

Relevant Log Output

No response

Anything else?

No response

@XenonSup XenonSup added the type:bug Something isn't working label Mar 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant