-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Auto upload from Android app fails if e2e app is enabled #39
Comments
Well..we (on android) create the folders if they do not exist. So the subfolders needs to be created before uploading and also being checked if they are / need to be encrypted... |
@tobiasKaminsky maybe create the structure on start of upload? |
We do not create them at all, but rely on webdav for doing this. @schiessle am I allowed to create these folders without a lock? I suspect not to, or? So I would first have to find the encrypted root folder and then lock it, create the subfolders and then unlock? :S |
it should be automatic on the server side for a subfolder of encrypted folder @schiessle |
As discussed with @schiessle, this is the way I am doing it now on android: |
This should be now fixed with latest commit: nextcloud/android@e335056 We will release a RC1 soon. If it happens again, please create a new issue on android github. |
automatically ? client side ? |
The auto upload of images is failing if the folder doesn't exist. I'm not sure if that is more an android issue or an issue with the e2e encryption app, but since it works without the app being enabled, I open the issue here.
NC version: 13 beta4
End-to-End Encryption version: 1.0.1
Android app version: 2.0.0
Auto upload is configured to use subfolders for year/month.
@nextcloud/android Can you have a look as well?
Server error log
The text was updated successfully, but these errors were encountered: