You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have enabled automatic image upload on my Android owncloud app. Suddenly I got Unknown error and the image could not be uploaded. When I looked at the server error log, I read the actual error message: 507 Insufficient Storage.
Expected behaviour
Why is not the server error used, which explains exactly what is going on. Unknown error is not very descriptive.
Steps to reproduce
Enable automatic image upload on your Android app
Set a too low quota on the server
Take a picture with your phone and wait for the automatic image upload
I don't know if this problem is specific to the photo upload. Maybe it concerns all upload when there is no space available.
Why is not the server error used, which explains exactly what is going on.
We don't show server errors as a general rule because HTTP error messages don't always explain in an user-understandable language what is going on, and because error messages are not internationalized.
We could consider using them just in the case of "Unknown error"s.
In any case, we need to improve this concrete error message, and some others.
Actual behaviour
I have enabled automatic image upload on my Android owncloud app. Suddenly I got
Unknown error
and the image could not be uploaded. When I looked at the server error log, I read the actual error message:507 Insufficient Storage
.Expected behaviour
Why is not the server error used, which explains exactly what is going on.
Unknown error
is not very descriptive.Steps to reproduce
I don't know if this problem is specific to the photo upload. Maybe it concerns all upload when there is no space available.
Environment data
Android version: Android 5
Device model: Huawei Honor 7
Stock or customized system: Stock
ownCloud app version:2.0.1
ownCloud server version: 9.0.3
Logs
ownCloud log (data/owncloud.log)
The text was updated successfully, but these errors were encountered: