-
Notifications
You must be signed in to change notification settings - Fork 42
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
Webdav encounters 403 authorization error after upgrade to 1.8.29 #403
Comments
Thanks for reporting. If you could provide a step-by-step on how to reproduce this error, that would be very valuable. Also, please provide as much technical info as possible about the WebDAV server. |
@Forge36 I just built an APK with just the WebDAV library downgraded, if you could try it out, that would be fantastic. To install it, you'll need to download one of the artifacts on this page, unzip the APK, transfer it to your phone and open it. (Or, if you have adb, you can use "adb install <apk filename>".) |
That works! I'm running
As it turns out that's also out of date (but doesn't report so), I'm manually updating my server, which will allow me to update the webDav server. I'll update if I continue to need the package downgrade after updating my server. Edit: updating to
Did not resolve this issue For reproduction steps, what are you looking for? |
For reproduction, just exactly what you are doing when the problem arises, and exactly what you are seeing. A screenshot is always good. Obviously, something has changed in the library we depend on, so they could have a bug, and if so we should report it to them. I'll downgrade the library for the next release, in any case. |
Two workflows tested:
I can include full logs via logcat if you'd find those helpful. The only entry that appeared relevant was (adjacent logs not clearly related to sync)
|
Looking at the dependency commits: Only two looked functional thegrizzlylabs/sardine-android@5d7883c and thegrizzlylabs/sardine-android@2365354 My URL does not contain spaces or percent encoding. Though I can't rule that out. The exists check is suspect combined with the other issue of some servers reporting 403 for non-existence. |
I've downgraded to 1.8.28 and disabled automatic updates in the interim.
Note: I upgraded to 1.8.30 and I'm still seeing the error.
The text was updated successfully, but these errors were encountered: