Support decrypting a folder in cloud storage about droidfs HOT 4 CLOSED

DroidFS use the original gocryptfs code to manage volumes. This code make syscalls to the underlying file system. Therefore, the gocryptfs volume must be on a real or virtual file system (like ext4, f2fs, fuse, etc). All of the app you see in the android file explorer side panel provide access to their content using a file provider: all file interactions pass through this app (using file URIs and Android APIs) before reaching the actual file (if it exists). Gocryptfs can't work like that: it only works with file paths.
If you want to use DroidFS on a volume synchronized in the cloud, you first need to download the volume, open it with its real path on the sdcard (not with android explorer side panel), and if you make modifications, upload changes with your cloud app. I tested this with Nextcloud and it works fine.
Another solution would be to modify the gocryptfs code to work with file descriptors from file provider URIs but it's a lot of work and will reduce performance because it would require much more interaction between native code and JVM. (I'm waiting for your pull requests ;D)

However, you discovered a bug: the selected path should be written in the "Volume Path" field. I will fix it in the next commits.

from droidfs.

Yes, the missing rights to write to the external sdcard is a real problem. Something like this should not be.

...

from droidfs.

1.2.0 released: you should now be able to open volume located on SD cards with read-only access.

from droidfs.

Issue documented in README (5da1c05), closing this one.

from droidfs.