Quote:
Originally Posted by stumped
ok but please try my suggestion of testing with the alternative calibrebox app to help establish if it is an app problem or a dropbox issue
i think the problem may be with the folder structure in dropbox not with the metadata.db file
https://play.google.com/store/apps/d...rebox&hl=en_GB
if calibrebox works where CC does not then it's a CC problem
if calibrebox does not work with your dropbox ( works Ok with mine) then its a dropbox problem |
Calibrebox works fine with my "corrupted or missing" library database. (It seems that calibrebox has a different strategy to synchronize databases: it does it on demand).
I more and more believe that
my guess is close to the real problem:
CC does not recover from a corrupted library downloaded by chance from dropbox (possibly while dropbox was updating it without a transaction protection).
If this were the case,
CC could "easily" solve the problem by not getting stuck in case it finds its own local copy "corrupted" when trying to compare, but
downloading the database in the cloudunconditionally (or asking for confirmation).
To continue using CC (the paid version, which I prefer to calibrebox, maybe for lack of experience) I had to create a new library and move my entire failing library to it. Sad.
Thank you again for the discussion