search

bpellin / keepassdroid

KeePass implementation for android
http://www.keepassdroid.com
Other
1.38k stars 346 forks source link

Database corruption when using Dropbox integration #99

Open trooley opened 8 years ago

trooley commented 8 years ago

When using a database stored in Dropbox, if I use Keepassdroid to add/amend entries then the new version of the database becomes unreadable by Keepass on PC - Keepass reports it as being corrupted. Fortunately the contents are recoverable using Keepass' import and repair function.

Database files stored locally on the Android device and then just copied to/from Dropbox after entries have been updated (ie not using Keepassdroid's Dropbox integration) aren't corrupted.

Reliably reproduced using v2.0.4, but it's been like this for a while so probably also in earlier versions.

Grossdm commented 8 years ago

Don't use the Dropbox app for Android; I had problems with it and tried Dropsync with complete success.

https://play.google.com/store/apps/details?id=com.ttxapps.dropsync

another link style:

market://details?id=com.ttxapps.dropsync

CRamsan commented 8 years ago

I have been using the Dropbox app with Keepassdriod with no problem. @trooley are you still using Keepassdroid + dropbox?

Grossdm commented 8 years ago

@CRamsan, Are you using the official Dropbox® app? It has been quite a while since I used it, but I found many problems with it. Lemme try to recall, list-wise.

  1. The app itself is much larger than it needs to be.
  2. It does/did not work like the desktop version by keeping everything (or a subset) synced. IIRC, it would fetch a file upon request. Files flagged as "offline" or "keep on device" (or whatever) were just a static file - not synced until you opened the Dropbox® app and accessed the file.
  3. Accessing the file: the Dropbox® app was THE interface to access the file. The "synced on demand" file(s) location was obscured by the app to manipulate users into using the app add the sole means of access.

I don't know if any of this has changed; I doubt it because of the plethora of apps similar to Dropsync in the Android Market (I just can't bring myself to say Google Play).

Dropsync runs in the background and does a good job of keeping the files synced nearly realtime - even better if you pay for the pro version. In both free and paid versions, ANY local changes are immediately synced. Oh, Dropsync begins by having you select the Dropbox® folder to sync and a local directory of your choice to keep the synced files. Thus, KeePassDroid knows nothing of Dropbox® and you don't have to install that bloated Dropbox® app. The KeePass database file is just always in sync - no need to think about it. I guess you could say it's a "Set it and forget it" thing.

Have all these issues been worked out with the official Dropbox® app? I'm curious.

Doug

CRamsan commented 8 years ago

Currently the official Dropbox app does work similarly to the desktop application and it will check for file modifications in the device and sync those changes without user input. Although this does not happen the other way around, which can be a big annoyance. But I have never had it corrupt a file. That would sound like a Dropbox issue to me. If there is no more actionable input I think this issue can be closed.

On Fri, Sep 9, 2016 at 9:43 AM Doug notifications@github.com wrote:

@CRamsan https://github.com/CRamsan, Are you using the official Dropbox® app? It has been quite a while since I used it, but I found many problems with it. Lemme try to recall, list-wise.

  1. The app itself is much larger than it needs to be.
  2. It does/did not work like the desktop version by keeping everything (or a subset) synced. IIRC, it would fetch a file upon request. Files flagged as "offline" or "keep on device" (or whatever) were just a static file - not synced until you opened the Dropbox® app and accessed the file.
  3. Accessing the file: the Dropbox® app was THE interface to access the file. The "synced on demand" file(s) location was obscured by the app to manipulate users into using the app add the sole means of access.

I don't know if any of this has changed; I doubt it because of the plethora of apps similar to Dropsync in the Android Market (I just can't bring myself to say Google Play).

Dropsync runs in the background and does a good job of keeping the files synced nearly realtime - even better if you pay for the pro version. In both free and paid versions, ANY local changes are immediately synced. Oh, Dropsync begins by having you select the Dropbox® folder to sync and a local directory of your choice to keep the synced files. Thus, KeePassDroid knows nothing of Dropbox® and you don't have to install that bloated Dropbox® app. The KeePass database file is just always in sync

  • no need to think about it. I guess you could say it's a "Set it and forget it" thing.

Have all these issues been worked out with the official Dropbox® app? I'm curious.

Doug

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/bpellin/keepassdroid/issues/99#issuecomment-245969336, or mute the thread https://github.com/notifications/unsubscribe-auth/AAqdc4lAwwhJsQ2BszzIPpfIYuOdSpNbks5qoYyXgaJpZM4H0aPO .

  • Cesar Ramirez -
Grossdm commented 7 years ago

Revisiting this still open issue, I just noticed that @bpellen recommends Dropsync on his website: http://www.keepassdroid.com

@CRamsan, I still suggest that you consider trying the Dropsync app. It just seems like a better app than the official version: smaller, more control, more transparent, and better synchronization. Dropsync does have a paid version that removes some restrictions, but the free app easily handles syncing the KeePass database. In fact, I've more recently started adding things for it to sync - I didn't have to change a single setting in the app; it just worked. No, I don't have any financial interest in Dropsync. 😆

Doug®

P.S./N.B. Who does need (or is able) to close this issue?

twt2 commented 5 years ago

Have there been any changes to this bug? I have been using KeePassDroid with Dropbox for years. I made three edits yesterday on my phone and today I discovered the database got corrupted when I tried to open the synced file on my laptop with KeePassXC. I verified it was corrupted on the phone, too. I was able to restore the prior version from Dropbox. I would rather figure out what happened so I can avoid it. As I have never had this happen before, is this a problem with the official Dropbox app that randomly eats data?