The communication with Onedrive works using authentication tokens. While the first request after Cryptomator freshly starts, we initiate a refresh token to refresh access. This token refresh process needs a user interface and thus displaces the biometric auth dialog which must always be in the foreground. As it is no longer in the foreground, it is terminated by os and causes an error that the biometric auth has been canceled. For this reason we start the enter password dialog.
Before 1.5.8 we had our own dialog which handled the fingerprint authentication and which was simply restored after obtaining the Onedrive authentication token and where this error was not thrown by the os, therefore the problem did not occur there...
If the unlock is restarted the authentication token to Onedrive is still valid which is why the biometric auth works in this case. Other clouds aren't affected by this bug.
We fixed this bug and will publish version 1.5.9 today (as always, updates must first be reviewed by google).
Most helpful comment
We fixed this bug and will publish version 1.5.9 today (as always, updates must first be reviewed by google).