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

Cannot delete vault from list. SQL error 19 #320

Open
2 tasks done
StanoRiga opened this issue Sep 22, 2023 · 2 comments
Open
2 tasks done

Cannot delete vault from list. SQL error 19 #320

StanoRiga opened this issue Sep 22, 2023 · 2 comments
Labels
type:bug Something isn't working

Comments

@StanoRiga
Copy link

Please agree to the following

Summary

When I try to remove a vault from the app I receive a SQLlite error and vault is not deleted

System Setup

  • iOS: 17.0.1
  • Cryptomator: 2.4.9
  • OneDrive 4 Businss

Cloud Type

OneDrive

Steps to Reproduce

  1. let you MS admin change authentication methods to „passwordless“ with MS Authenticator😀
  2. try to delete the onedrive connection because you can’t access your vault and want to set up the connection again (because it works on the iPad without MS Authenticator installed)
  3. fail some times and try and try again until you notice that the connection is was finally deleted
  4. Notice that the vault to that onedrive connection is still available in the vault list
  5. Try to delete the vault
  6. Get the error.

Seriously, I am not able to set up a onedrive 4 business connection because it always triggers MS Authenticator to show up, even before the MS login is coming up.
By trying over and over again, it seems I somehow managed to mess up the vaultaccounts table.

Expected Behavior

Vault is deleted from list

Actual Behavior

Error message pops up
IMG_0889

Reproducibility

Always

Relevant Log Output

No response

Anything else?

No response

@StanoRiga StanoRiga added the type:bug Something isn't working label Sep 22, 2023
@StanoRiga
Copy link
Author

As I wanted to use my OneDrive vault on the iOS device again, I deleted the app and reinstalled it. After that, the problem was (unsurprisingly) solved.
I leave it to the developers to leave this topic open or close it.

@tobihagemann
Copy link
Member

Sorry that we didn't respond. I'd like to keep it open since it hasn't been resolved.

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

2 participants