I got a new android phone and install Cryptomator on it. But when I try to connect to open an existing vault via Google Drive, I get a message that says “An error occurred”. I am able to create a new vault via OneDrive, remove it, open it again via the “existing vault” option, but I can’t do the same with Google Drive. I can still access the vault via my Windows Desktop PC.
Steps I’m taking:
Install Cryptomator
OpenCryptomator
Accept permissions for notifications
Tap the + icon
Choose add existing vault
Choose Google Drive
Select the account where the existing vault resides
Receive error “An error occurred” on the screen where I’m supposed to select the masterkey file.
Specs:
Cryptomator version 1.11.1 for Android, downloaded from the Play Store
Have you tried doing the same thing on Google that you did on Microsoft OneDrive where you added a new Vault rather than opening an existing vault? Does that work?
Can you open the standard Android Google Drive app and access that Google account and see your Vault files encrypted?
I’m thinking that it might be permissions related. If you go into cryptomator and tap on the three dots in the upper right corner to go into settings there is an option for cloud services and in there you’ll know whether or not you are logged into Google or not and if you are, you might want to try logging out and logging in again. I’m guessing that you’re not properly authenticated yet.
I can open the Google Drive app and see the encrypted files. I can also confirm I’m signed in to Google Drive in Cryptomator by going to Menu > Cloud Services. I’ve tried logging out and back in and I’ve even uninstalled Cryptomator and reinstalled it. No Change.
I just tried to create a new vault in Google Drive (just like I did for OneDrive), and I also get the same error message. (Create new vault > Google Drive > Enter name > tap “create” > receive error.)
I agree that it may be permissions, but I’ve given the Android app all the permission available. (Notifications & Photos and Videos).
There is one other thing you can try. Sometimes Google may have issues with apps being granted permission to access your Google Drive and this software has previously been granted access. You can go into Google’s security settings and check for cryptomator. If it’s there remove it which will force the software to reapply for permissions to access your Google Drive.
App Permissions: Go to your Google Account’s security settings and review “Third-party apps with account access.” You can try revoking Cryptomator’s access and then re-adding the vault in the app, which might force a new, successful authentication flow.
The only other method I can think of would be to at least temporarily bypass cryptomator Google connectivity and use another program to gain access to your Google Drive. I don’t know how strong your computer Android tech skills go but there is an app that you can load on your phone that will act as a file system provider for Google Drive files and let cryptomator get to the vault through that program.
If you feel comfortable you can go to GitHub in read up on the software and see if you feel comfortable installing it. I can answer questions you might have getting started. It’s an app called RSAF. It can let you access your Google Drive and your vault from cryptomator.
It’s a two-step process. First you install and set up the software to access your Google Drive and enable local file access privileges in the app.
The next step is to go into Cryptomator and point it at the local file system which will redirect it to Google Drive. I know how to do it all I just don’t have it documented for others to read. I figured it out on my own in you might be able to also if you’re comfortable enough with Android software.
Rsaf will let cryptomator think that it’s accessing local storage when it’s really being redirected to your Google Drive.
If you feel comfortable giving it a try I can answer questions if you get stuck.
Try removing the software from Google and then reauthenticating to Google and see if the error goes away first that way.
I still haven’t heard back from support, but I was able to figure out the issue. My account uses the Google Advanced Protection feature (Advanced Protection Program). When it’s enabled, I Cryptomator can’t access the account. But if I disable it, Cryptomator connects and works as expected. Once it was working, I re-enabled the Google Advanced Protection feature, and so far Cryptomator is still working. I try again tomorrow and see if it still works.
If it does, then it’s just matter of disabling the feature during the initial setup. Otherwise, Cryptomator needs to be updated to support the more secure connection options that are supported when Google’s Advanced Protection features are enabled.
Glad to hear you got things going for yourself. Google security is always changing over the years and I’m moving my email away from Google and over to an independent mail provider with encryption.
I’ve been routing my personal domain email through Google for a few years and now the security things that they’re implementing are making it more difficult for me to continue using them for mail. I’ll be off Google Mail in about a week when I’m done transitioning my data off and moving to a new secure email server.
I like to keep all of my email encrypted on the server even if I’m not communicating directly with somebody end-to-end encrypted.
I sent the debug report on 9/23, but have not heard anything back yet. After re-enabling the Google Advanced Protection Program , I can no longer access my vault. It seems that this happens for applications that do not support the more secure connections to Google’s systems. Is there a plan to fix this?
