Cloud services in the iOS app: recommended providers, Google Drive limitations, and WebDAV

With the Password Depot iOS app, you can open and save databases directly in a cloud service and thus always use the same state on iPhone, iPad, and PC. This article summarizes which services have proven themselves, which limitations currently apply to Google Drive, and how to connect your own storage via WebDAV – for example, MagentaCLOUD.

Recommended services and correct folders

You establish the connection via Open DB manager: select the service and sign in; to sign out, tap the menu in the top right and then Disconnect.

• For use across devices, OneDrive, Dropbox, Box, and HiDrive are supported. We currently advise against Google Drive for the iOS app (see below).

• Password Depot uses a fixed default folder for each service, for example Dropbox \Apps\Password Depot\, Google Drive/Box/HiDrive \Password Depot\, OneDrive \Files\Documents\Password Depot. Do not create these folders manually and do not change them – in the cloud, the app only sees its own permission scope. Let Password Depot create the folder (e.g., when creating a new test database). The most common cause of "database not visible" is a file in the wrong folder.

• If signing in to the cloud service fails with an older app version, update the app first: the providers block outdated sign-in methods.

Google Drive: database suddenly no longer visible

Google no longer makes the former, far-reaching "Drive" permission available to new apps. Password Depot therefore uses the restricted "drive.file" permission: the app sees and edits only files that it created or saved itself. Manually uploaded databases – for example, via the Google Drive web interface or from another device – remain invisible to the app. This requirement by Google cannot be bypassed and affects Password Depot's Google Drive integration as a whole.

To restore access to a "disappeared" database:

1. Download the database to your device via the Google Drive web interface.

2. Import the downloaded file into the Password Depot app.

3. Save the database to Google Drive again via Save as. This creates a new file that the app can access permanently.

Also check in the web interface whether several "Password Depot" folders exist – this too causes visibility conflicts; merge the contents into the default folder. If you want to avoid these limitations permanently, switch to another supported service.

Setting up WebDAV (MagentaCLOUD, Nextcloud, your own server)

Via WebDAV, you connect storage that is not directly integrated; you need your provider's WebDAV address (URL), your username and password, and, if applicable, the path to the database folder.

• If you experience timeouts or dropped connections, increase the timeout value of the WebDAV connection.

• MagentaCLOUD: Do not sign in with your Telekom password. Create a session password in the MagentaCLOUD settings and store it in Password Depot.

Note: Databases that the Windows client saves with the new encryption (Argon2id/AES-GCM) as of version 19 currently cannot be opened by the mobile apps. For databases shared via the cloud, choose PBKDF2/AES-CBC for now.

Related topics:

• Where does Password Depot store databases when I use Dropbox, OneDrive, Google Drive or Box?

• I can no longer log into the cloud using the Password Depot iOS app

• Where does the iOS app store my databases – and what to do if they are missing after an iOS update?

• New encryption options in version 19 (Argon2id, AES-GCM): What do I need to consider with mobile apps and older versions?