search

cryptomator / android

Cryptomator for Android
https://cryptomator.org
GNU General Public License v3.0
761 stars 127 forks source link

Like to access vaults in other apps via "local storage" like proton drive or sync #538

Closed L9845 closed 5 months ago

L9845 commented 5 months ago

Please agree to the following

Summary

Access to web services via webdav and s3 is great, but some services don't have that

Motivation

Alot of services are using e2ee and you have to use their apps in order to use the service. Great, nothing wrong with that. On android, or other secure android roms you can access the contents on the services via the files app. The problem is when you go to create a vault or open an existing vault cryptomator for some reason only sees the phones storage. I will like cryptomator to "see" storage from other apps. And I will like to explain, I don't want to give an app access to a cryptomator vault. Like a notes app in which the note app accesses cryptomator and reads, and writes the vault. I want cryptomator to be able access the contents of an app. Being able to create and access a vault in proton drive or sync, etc.

Considered Alternatives

No response

Anything else?

No response

SailReal commented 5 months ago

Thank you for your feature request, but if I understand correctly, this is a duplicate of https://github.com/cryptomator/android/issues/86

derei commented 4 months ago

@SailReal ...I see issue #86 is quite old and is been left to grow moldy. At the same time, this issue has been marked as duplicate and closed as completed. Was the feature added in cryptomator, or the decision was to disregard it? Thing is, people will keep making new issues related to better file management, as long as the situation remains unclear.

Thanks.

JaniruTEC commented 4 months ago

Hello derei,

while #86 has gathered some dust, it's still open and might be picked up in the future. As far as we understand, this issue is a duplicate of #86 and was marked as such. If you believe that's an error, please let us know. If it's not an error, #86 is the place to go for all future inquiries regarding this issue and this issue here can be closed. We sadly only have two options for closing an issue, "Completed" or "Not planned", both of which don't really have a right ring to them. That's why my colleague picked the more conciliatory "Completed". The feature has not yet been added but there has not been made a decision to disregard it, either.

I hope that clears things up! Kind regards JaniruTEC