I am using a self hosted Stalwart mail server with CalDAV.
When adding a new standard event to this calendar in the desktop client it does not show up in the android app and when doing the same in the android app it does not show up in the desktop client.
When looking in other clients (tested Thunderbird and BlueMail) both events are visible.
It seems eM Client is successfully creating events on the server but isn’t retrieving existing events from the server on both the desktop client and the Android app.
I did see on sleekplan that calendar support for mobile versions is still in BETA but afaik I’m not using any BETA version on my android phone.
When adding a new standard event to this calendar in the desktop client it does not show up in the android app and when doing the same in the android app it does not show up in the desktop client.
When looking in other clients (tested Thunderbird and BlueMail) both events are visible.
Yes eM Client mobile app and Desktop does support CalDAV as long “as you have the correct CalDAV url in both” so could be the Calendar URL possibly is “missing something in the link” that needed for eM Client on desktop and mobile. Or could be you need the later mobile Beta app.
So to try the Android Beta mobile app, go to the Playstore and in the eM Client app “scroll down and you can signup for the Beta version”. Then install that and see if your CalDAV url syncs.
If it still doesn’t email [email protected] for assistance with the Beta mobile app.
I have the same experience here, thought it’s my fault, but I tested the Stalwart CalDAV Server with Thunderbird and Apple iPad, they work with Stalwart, but eM Client does not receive any Events, just sent them. I tried all the different endpoints but no luck.
Must be a compatibilty issue but on which side?
Thank you for the test account. We’ve made the testing and identified the server’s behavior that goes against the specification. We will contact the authors of the server code in order for them to fix that and/or (based on the response from them) we will try to make an workaround for the issue.