@Aurel-P This is always occuring when you import erroneus vcf directly into the Synology. Synology does not correct these vcfs and on DAVx5’s request the server crashes by delivering these data.
Please delete the address book.
Create an empty one and make a DAVx5 account connected to this new address book.
Then import the vcf files directly on Android into this new account.
Then it should work.
I’m almost sure my issue has little to do with DAVx⁵ but I would still like to ask my question in the hope to get directions where to go/ what to research.
I am using the horde server via CPanel. All works reasonably well but I can’t create a new calendar from the app. I get a pop-up with the following message:
java.io.IOEsception unexpected end of stream on https//[url].nl:2080/...
Now this is probably a restriction from my host. I couldn’t find the issue here or anywhere else so I think I’m on my own. But it might be horde. I don’t think ints DAVx⁵ because the same issue pops up if I use another sync app.
Any clue if I can fix this myself? Where do I look?
(fyi: host sais (litterally): “we do not support caldav. Be happy it works mostly!” - they are cheap, I don’t complain - and somehow I don’t expect a lot from horde support hence I’m posting here. Hi!)
Indeed, it’s technically possible to tell the Calendar API a different email address than the account name (default is account name). We’re planning to make an “email address” CalDAV account setting in DAVx5 for this purpose. However, at the moment, the account name will be used as email address.
That would be great, thanks for planning that!
You have renamed the account to a name that’s already existing. DAVx5 didn’t handle this error properly, but it should now be fixed (show an error message instead of crashing).
It is likely possible these entries 23 and 24 in the service DB came from an old backup that failed. I didn’t have an account listed in the app with that name already.
Thank you for having improved that!
Perfect, so I’ll set this as solved.
Absolutely. We hear this from time to time, and I have often tried to reproduce it, but never succeeded. If you find a way to reproduce this, please let us know in a new thread.
Hello and yes, the new version is working - at least within the browser interface of mailbox.org.
I’m looking forward to seeing this version in F-Droid.
Within my android mail app (FairEmail) it doesn’t work but since it works generally I’ll contact the developer.
Thank you very much!
I imported my calendar events on my Android via an app called Calendar Import-Export and it contained events from long ago until now. Do you suggest I remove the older events and give sync a try again?
Will 126.96.36.199 be released on F-Droid? I’ve started experiencing this same exception yesterday with a FastMail calendar on 3.2.1. (Wouldn’t surprise me if it also had to do with a Google Meet event, since I have a couple of those.)
Sorry for the comment in German… Here the translation:
I informed the mailbox.org-Support about this issue and they filled a bug report to Open-Xchange. They confirmed it’s a bug and ones a patch is available, mailbox.org will test and roll-out.