# Latest android Joplin began to fail WebDav synchronization

**URL:** <https://discourse.joplinapp.org/t/latest-android-joplin-began-to-fail-webdav-synchronization/3906>\
**Category:** Support\
**Created:** [14 October 2019 10:28 UTC](https://discourse.joplinapp.org/t/latest-android-joplin-began-to-fail-webdav-synchronization/3906 "2019-10-14T10:28:44Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![laurent](https://avatars.discourse-cdn.com/v4/letter/l/ce7236/32.png) [@laurent](https://discourse.joplinapp.org/u/laurent)\
**Post date:** [21 November 2019 11:45 UTC](https://discourse.joplinapp.org/t/latest-android-joplin-began-to-fail-webdav-synchronization/3906/10 "2019-11-21T11:45:23Z")

</div>

@Rado1, your server redirects `.lock` to `.lock/`, which is useless, but it does it anyway. This causes an issue in Joplin (in iOS for sure but maybe in Android) too because when a request is redirected, the underlying network stack doesn’t forward the auth headers.

You might want to try the latest version 311, which fetches `.lock/` directly, to see it solves your problem:

> **[laurent22/joplin-android](https://github.com/laurent22/joplin-android/releases)**
>
> Android releases for Joplin. Contribute to laurent22/joplin-android development by creating an account on GitHub.

---

_[View the full topic](https://discourse.joplinapp.org/t/latest-android-joplin-began-to-fail-webdav-synchronization/3906)._