You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My PassDrop data exists inside Dropbox/Apps/PassDrop/. I don’t recall if PassDrop chose this, or if I did it manually, because that’s the most common app-data filename scheme for Dropbox linked apps.
I just tried linking a new phone to my PassDrop and was quite confused when I successfully linked, but nothing displayed. I even verified the KDB existed in its proper place
Ultimately I discovered you have to pretend you’re adding a “new” KeePass database, which in my opinion suggests inherently that you’re creating a new empty database from scratch.
My suggestion is to:
Standardize upon /Dropbox/Apps/PassDrop/ if not already doing so.
Upon Dropbox link, populate main PassDrop screen DB list with the .KDB’s present in the aforementioned folder.
I believe this UX more closely aligns with what users have come to expect nowadays in terms of reusing familiar app UI paradigms.
The text was updated successfully, but these errors were encountered:
My PassDrop data exists inside Dropbox/Apps/PassDrop/. I don’t recall if PassDrop chose this, or if I did it manually, because that’s the most common app-data filename scheme for Dropbox linked apps.
I just tried linking a new phone to my PassDrop and was quite confused when I successfully linked, but nothing displayed. I even verified the KDB existed in its proper place
Ultimately I discovered you have to pretend you’re adding a “new” KeePass database, which in my opinion suggests inherently that you’re creating a new empty database from scratch.
My suggestion is to:
I believe this UX more closely aligns with what users have come to expect nowadays in terms of reusing familiar app UI paradigms.
The text was updated successfully, but these errors were encountered: