![]() ![]() Google drive should not allow to modify file in trash and somehow keepass2android made it possible to create 2nd instance of this file. So Philipp, you are right, there are 2 files in google drive (one actual and one in trash), but something is buggy. History shows that this file was modified afterwards (in august and september, it looks like keepass2android somehow used the entry from trash, which answers the question why the file was in "sync" but i havent seen the changes neither in google drive nor on my PC) Was moved to trash on July 25th (it does not make sense, but could be date on which i made restore on my new android device) was uploaded(not created!) to google drive on July 25th (It does not make sense, because I have using this file for couple of years).The July 25th could be a date when I port my data. In July I bought my Samsung S7 mobile phone and i move all my apps and data from Nexus 5X to Samsung S7. Essentially it will save a copy of your db on Google Drive for you to open on your phone using KeePass2Android. Client ID/Secret from your google account. From there you need to follow a few steps to get it working. So something happend in July?! Somehow keepass2android has used db file from trash.and not the actual file. All you need is to install the 'google sync plugin' for keepass. My actual pavol.kdbx file was uploaded to drive on July 25th. It was created back in 2014 and moved to trash on July 25th and the history says, that this file was modified after move to trash. I have found one entry with name "pavol.kdbx" in trash of my google drive. I have been using this file for couple of years. ![]()
0 Comments
Leave a Reply. |