We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Photos should upload and clear out of Transfers screen
Transfers
Photos do seem to upload, but the photo remains in the Transfers screen with error: `
If applicable, add a screenshot showing the issue.
Liquid for iOS 4.1.0.17 © 2021 2021-12-19 14:42:29 Network completed upload file: https://domain.mydomain.org/remote.php/dav/files/username/Photos/21-12-19 14-41-31 7815.jpg with error code 503 and error description 503: The server is temporarily unavailable
iOS version: e.g. iOS 15.1.1
Nextcloud iOS app version: see More > Settings
4.1.0.17
Server operating system: Ubuntu (nextcloud VM)
Web server: Apache
Nextcloud version: see Nextcloud admin page 22.2.3
The text was updated successfully, but these errors were encountered:
And just for reference, the WebDAV server is up and running. I can upload files to it fine using the nextcloud web interface.
Sorry, something went wrong.
#1788
Closing in favor of #1788
No branches or pull requests
Steps to reproduce
Expected behaviour
Photos should upload and clear out of
Transfers
screenActual behaviour
Photos do seem to upload, but the photo remains in the
![image](https://user-images.githubusercontent.com/10717998/146688555-01a1677a-d056-4e15-bb9e-bf6aec00eac9.png)
Transfers
screen with error: `Screenshots
If applicable, add a screenshot showing the issue.
Logs
Reasoning or why should it be changed/implemented?
Environment data
iOS version: e.g. iOS 15.1.1
Nextcloud iOS app version: see More > Settings
4.1.0.17
Server operating system:
Ubuntu (nextcloud VM)
Web server:
Apache
Nextcloud version: see Nextcloud admin page
22.2.3
The text was updated successfully, but these errors were encountered: