Cannot sync with webdav

[mke21]

After having had problems syncing to Onedrive, I changed to using the WebDav cinnection in my StackIp account. This works fine on both my Linux and Windows Laptop. However it does not work on my iPhone 8. Error is PROPFIND /:UnknownError,]

Seems to be similar to #2103.

Environment

Joplin version: 12.8.1 (iOS)
Platform: iOS
OS specifics:15.6.1

Logfile

[Wartijn]

Possibly the same issue as #6249

[mke21]

that one is closed but not fixed?

[Wartijn]

Yes, if there isn't any activity on an issue, it gets closed. I didn't leave a comment to keep the issue open, because I switched to Dropbox as a backend, so it wasn't really easy for me to check if that bug was still occurring.

But this could be the same issues (Like I mentioned in my bug report, I suspect Joplin adds an extra slash to the url)

Do you get the error when you click on Check synchronization settings or only when actually trying to synchronize?

[mke21]

I only get the error when synchronizing, the Check just passes. I guess it's indeed the same problem as discussed in #6249

[github-actions]

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? If you require support or are requesting an enhancement or feature then please create a topic on the Joplin forum. This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.

[mke21]

This is still not fixed and the lack of reaction is a bit disappointing. But bumping this to keep it open.

[Heziode]

Same freaking issue for months on iOS and MacOS…

This is not fixed, but, since this project is maintained by only 1 person, @laurent22, this may explain why it is still not corrected, it can't be everywhere at once.

It might be time to delegate some of the project management to other people, in order to merge more and have faster fixes.

[mke21]

I'm not as much concerned with the fact that it isn't fixed. I can understand that this does not happen overnight, but with the fact that Github tried to close it because there has been no activity on the issue. I'm wondering how many issues are being automatically closed without anyone looking at it. A simple aknowledgement would have been sufficient.

[github-actions]

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? If you require support or are requesting an enhancement or feature then please create a topic on the Joplin forum. This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.

[Heziode]

Still have this issue, using kDrive by Infomaniak (it's a Nextcloud).

[mke21]

Yup, me too and after two months still nobody bothered to even put this on the list of to be done which is quite worrisome. I've relucantly reverted to using onedrive but would still love to use the WEBDAV as advertised.

And with nobody from the development looking and the github bot keeping on trying to close this, this will probably never be fixed.

[Heziode]

On my side, I moved to Notesnook.

[mke21]

Just leaving a remark in the hope it gets noticed....

[github-actions]

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? If you require support or are requesting an enhancement or feature then please create a topic on the Joplin forum. This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.

[mke21]

Any update on this?

[Thulkash]

Same issue. Is this could be fixed please?
I'm starting to consider going back to Android...

[mke21]

Half a year and no reaction, neither on the forum, nor here. Don't think this will be fixed anytime soon.

[github-actions]

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? If you require support or are requesting an enhancement or feature then please create a topic on the Joplin forum. This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.

[github-actions]

Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, feel free to create a new issue with up-to-date information.