Closed GoogleCodeExporter closed 8 years ago
I'm facing the same issue with Samsung Galaxy s3. It happens with the .key file
as well. You can bind your .kdbx file via Google drive with "Open with..." but
not the .key file.
Original comment by dekinder...@gmail.com
on 7 Aug 2013 at 10:35
Original comment by bpel...@gmail.com
on 19 Aug 2013 at 12:37
Same same for me ...
Original comment by Michael....@gmail.com
on 9 Sep 2013 at 8:11
Was there a resolution to this problem? I'm having the same issue: New user. SW
works great on Win 7 PC, put database and key file in Google drive folder.
Found them on Galaxy 10.1. Same error as above. Made files available offline,
no joy. tried to connect using URL of Google files, still no success.
Original comment by seanmc...@gmail.com
on 18 Oct 2013 at 4:27
I had this problem. All I had to do was go to google drive, click on the
passowrd file and it opened up in KeePassDroid. All good.
Original comment by clob...@gmail.com
on 25 Oct 2013 at 6:49
I have the same issue. Can figure work around for the db but not the key file.
I have even downloaded it locally and chopped to a different folder for good
measure. Still having issues. Anyone resolve this problem before I revert to a
stops spread sheet on drive?
Original comment by tzi...@gmail.com
on 27 Mar 2014 at 1:29
Going to google drive and opening the database file from there worked for me. I
used the Google drive app to double click on my keepass database. From there it
asked me what app do I want to use to open it. I chose Keepassdroid and it
opened up with no issues.
Original comment by dward...@gmail.com
on 14 Nov 2014 at 2:14
Original issue reported on code.google.com by
mties...@gmail.com
on 3 Aug 2013 at 4:14