Closed GoogleCodeExporter closed 9 years ago
I believe this is likely due to Google's mucking about with SD card storage
permissions in KitKat. If rooted there is a fix... but for the rest of us, if
your manufacturer didn't enable full sd writing, then we are out of luck. They
claim it is for better security... app developers are only allowed to write to
an application specific folder (and uninstall of app WIPES this folder, btw.)
[Security claims don't seem to ring true, because these same apps have full
read/write access to the INTERNAL storage... which many phones, that's all they
have... hmmm?]
Anyway, I'd like to see this updated so we can at least write to the SD card...
but everyone needs to be aware that uninstalling the app will mean loss of the
database file... so BACKUP!!
I'm trying to hold off Kitkat update for now...
Original comment by davidc7...@gmail.com
on 13 Mar 2014 at 9:09
It is frustrating that Google has removed general write access to "external"
storage in KitKat. It's going to make many Files managers and generalized
syncing tools (Dropbox/Dropsync) unusable.
It does appear there is no permission KeePassDroid can request in order to
write to the the sdcard.
I'll probably respond by updating the app to offer to save to the app specific
directory, if it fails to write to the database's location.
I'll probably also start looking into the Storage Access Framework[1]. It looks
like Google is intending this as its replacement for the file system on the
phone. This may be a positive development overall since it looks like this will
allow better integration with cloud storage providers (if they implement it),
without needing to add the internet access permission to the app.
[1] https://developer.android.com/guide/topics/providers/document-provider.html
Original comment by bpel...@gmail.com
on 13 Mar 2014 at 10:02
Issue 662 has been merged into this issue.
Original comment by bpel...@gmail.com
on 24 Mar 2014 at 3:27
Issue 663 has been merged into this issue.
Original comment by bpel...@gmail.com
on 24 Mar 2014 at 3:28
Issue 667 has been merged into this issue.
Original comment by bpel...@gmail.com
on 24 Mar 2014 at 3:28
Issue 666 has been merged into this issue.
Original comment by bpel...@gmail.com
on 24 Mar 2014 at 3:28
Issue 668 has been merged into this issue.
Original comment by bpel...@gmail.com
on 24 Mar 2014 at 3:28
Issue 669 has been merged into this issue.
Original comment by bpel...@gmail.com
on 24 Mar 2014 at 3:29
Issue 670 has been merged into this issue.
Original comment by bpel...@gmail.com
on 24 Mar 2014 at 3:29
There's no way for me to give the app the ability to write to these sdcards.
However, in version 1.99.11, the app let's you know when you open a database if
it is read only.
Original comment by bpel...@gmail.com
on 24 Mar 2014 at 3:30
Sony Z Ultra 4.4.2 use 1.99.11 still have problem
Original comment by sir...@gmail.com
on 31 Mar 2014 at 1:00
I don't understand how this issue is "fixed". If you have an existing
database, you can open it for reading, but then you cannot save changes to it,
nor are you given the choice to save the database somewhere else. Expected
behavior: saving changes works without error, or at least gives you the option
to save the database somewhere new.
This is using KeePassDroid 1.99.11 on a Droid Razr M with Android 4.4.2.
Original comment by jwei...@forbes.com
on 30 May 2014 at 6:52
Using keepass ver 1.99.11 on Samsung S5 active with Android 4.4.2 and this bug
occurs, that I cannot write to the database.
Issue is NOT fixed!
Original comment by fam...@gmail.com
on 3 Sep 2014 at 10:32
Android 4.4.2. This bug happens even with internal storage when try open
keepass file from GoogleDrive. But it's works fine with Dropbox.
Original comment by alexsn...@gmail.com
on 18 May 2015 at 5:36
Original issue reported on code.google.com by
letouris...@gmail.com
on 28 Feb 2014 at 1:29