-
-
Notifications
You must be signed in to change notification settings - Fork 24
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
Can't write files into Nextcloud #116
Comments
Can you be more specific about what you are doing and seeing? I tried reproducing with your environment and found that I couldn't even create a file in Nextcloud—creating the blank file failed: Trying with a different provider (Dropbox) I found that what happened was:
If this correctly describes your issue, then I have identified the cause and will release a fix soon. If not, please give more detail. |
I noticed that I can't create a new file in Nextcloud from your app (an error appears), so I thought I could use it to edit existing org files instead. Editing an existing org file in Nextcloud seems to work, said snackbar appears, but when I open the "saved" file in the Nextcloud app afterwards, it is still empty. |
OK, thanks, what I described is a different bug, then. It will be fixed in v1.45.3. I can reproduce your issue as well.
Orgro is doing the same thing regardless of source app, so the fact that it works with some and not others indicates to me that it's a problem with the source app. I don't think there's anything I can do about it. If there is another app that can access files in the same way as Orgro (via the File Provider API) that can successfully write to Nextcloud or Google Drive files, then that would indicate a problem with Orgro. I will have to see if I can find such an app. |
Looks like you might be correct here: I'll leave this open for verification if you wish / close as you please. Sorry! |
Nice find! Thanks for that. Let's keep this open as a tracker. |
orgro 1.45.2, iOS 18.1, Nextcloud 6.1.1 on Server 29.0.4.
The text was updated successfully, but these errors were encountered: