Permission Denial: writing android.support.v4.content.FileProvider uri content://org.cryptomator.beta.fileprovidor/decrypted/filename.ext

[earthsound]

Basic Info

This is a bug report / question or something else.

I'm using Android in version: 6.0.1

I'm running Cryptomator in version: 0.4.1

Description

I cannot save or merge a kdbx file back to Cryptomator vault.

Steps to reproduce:

1. Install Dropbox, Keepass2Android, and & Cryptomator
2. In Cryptomator, create new vault within Dropbox
3. Upload kbdx file into vault
4. Open kdbx file from within Cryptomator > should prompt to open with KeePass2Android
5. Edit file > Save

I receive this error:

Could not save to remote: 
Permission Denial: writing android.support.v4.content.FileProvider uri content://org.cryptomator.beta.fileprovidor/decrypted/filename.kdbx from pid=26855, uid=10261 requires the provider be exported, or grantUriPermission(). Save again or use the Synchronize menu when remote connection is available again. 

Attempting to synchronize results in the same error message minus the last sentence.

---

Is this an issue with KP2A, Cryptomator, a combination of the two, or limitations with the OS?

On a side note, if I upload an RTF file into a cryptomator vault and edit it with ES File Explorer's "ES Note Editor," when I save it I get no error but going back to the vault shows that the file wasn't changed.

Did I miss reading somewhere that this it's read only on Android?

[earthsound]

I opened a ticket at KP2A's CodePlex site and the dev answered:

It's an issue with Cryptomator that they do not serve their vault contents through the Storage Access Framework as a document provider.
Please see #35

If Cryptomator on Android doesn't implement SAF, how are we to use it for anything other than reading files?

[tobihagemann]

Thanks for the additional information! Just saw that we've stated in #50 (comment) that we're going to add SAF support.

@markuskreusch How should we manage this issue? Would this bug/error remain for Android <5.0 or is there something else that we can do about it? Should we update #35 somehow so that it reflects our plans?

[markuskreusch]

#50 is related to supporting the SAF as backend for storing our encrypted files. That is different from making the vaults contents accessible via the SAF. This is what #35 is about. I think #35 already states what we plan. In general this is not really a bug but only caused by the SAF feature missing during the beta.

#6, #15, #40 all seems related to this. I will have a look at that and consolidate those issues if possible.

We will adress this. Not sure about the possibilities in Android < 5.0.

Workaround
Do not save the file but create a copy, edit it and then add this copy back to the vault.

[markuskreusch]

Closing this in favor of #15