Could not save to source file: Permission Denial

[pauldel]

after exporting my kdbx file to downloads (then copying it to a flashdrive & deleting it from downloads) I started getting an error when saving an edited entry;

Could not save to source file: Permission Denial: writing come.android/providers.downloads.DownloadStorageProvider uri content://com.android.providers.downloads.docments/doument/msf%3A22 from pid=25666, uid=10221 requires android.permission.MANAGE_DOCUMENTS, or grant UriPermission(). Save again or use the Synchronize menu when file is accessible again.

I tried saving again and synchronizing, the latter throws another error message: Exception of type 'keepass2android.lo.Document AccessRevokedException' was thrown"

If there's a better place to report this please advise. Love the app, only thing is I do want to understand all the places my password file is stored.

[starbuck3000]

I am getting this exact same issue after resetting my smartphone to firmware defaults. I am getting worried because I have already changed 3 or 4 accounts since and when I transfer the file to another computer, I am getting an older version of the database.

I see no updates on this issue for more than 2 years, does that mean I should stop using the app until this gets solved?

[TimMensch]

I just came across this because I had a similar problem, though mine came up with "File not found."

And infuriatingly, the "export database" option would only ever export a stale version of the database!!

No matter what I did, selecting different source files, deleting references to source files, selecting cache files...everything I could think of as a software engineer, the new passwords I created were all still available on Android but absent in the exports.

So I killed the app (Force Stop) and re-ran it.

POOF! All the new passwords gone!

WTF is up with an export that doesn't actually export the current passwords?!

But yes, it's really annoying when software doesn't work the way it should. :(

[starbuck3000]

Hi. If it can help, I am now using a workaround. While the database is opened, click:

• more (three dots)
• settings
• database
• export database (choose: keepass 2 database)
• in the filesystem prompt, do not choose the file from which the database is being loaded but create a new one.

I ended up having a "mydb.kdbx" as my ongoing database and "mydb-export.kdbx" as the exported database. I only move out the "-export" file now. No more cache/overwrite/merge errors, and no more entries lost.

[KyleSCraig]

I had this error for a few months and fixed it today.

For me, I had migrated the database from my computer and opened it from my Downloads folder. When I later went and deleted old backups, the file which was recorded as being the source ceased to exist. For me everything kept working fine despite the error and my exports contained changes. Here's what worked for me to fix it.

1. Export the database (and I also checked opening it on my computer to confirm it was up-to-date)
2. Open that export (at this stage the error is gone, but it could easily come back)
3. Import database to internal folder (found just below the Export button, this stores the database in a place you won't delete)