-
-
Notifications
You must be signed in to change notification settings - Fork 53
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
Event created on iPhone cannot be altered on Mac #135
Comments
I redacted my email address in the log as a rudimentary precaution. Log in next post. |
|
I have this issue as well. At first I thought it was just happening to events past the current time but it happens to all events created on iPhone. I usually copy the event and then delete the original. But even delete the original I have this issue (the deleted event will pop back up again). |
This still happens. My work around is to use the browser version but even when using that it has some issues with recurring events. When editing on browser it will cause events to not update/show up in the macOS calendar. It work on iOS and iPadOS though. I feel like I can only use the desktop versions to look at the events and I just need to edit them on mobile later on. I would like to just have a UI for the desktop version that I can press a refresh button and know that what I working on will be sent and updated and any new event will be pulled as well. |
Sorry for the slow reply. @XxBlackHatxX, what exactly is it saying when it tells you the event can't be edited? |
Version Info
iOS: 13.5
etesync iOS: 1.3.5
macOS: 10.15.5
EteSync DAV: 0.18.1
Radicale: 3.0.2
Reproduction:
iPhone > Cal > Create event with title i.e. "Sport iPhone A"
iPhone > etesync > Start sync (as of now it will otherwise NEVER arrive at server, needs manual pushing)
Mac > Cal > Wait for next pull event (is set to "every minute" but de facto it is often 2-3 minutes)
Mac > Cal > Edit event title (add some characters) i.e. "Sport iPhone A Mac 1" --> 2-3sec later the input gets visibly discarded again
See full log in next post.
The text was updated successfully, but these errors were encountered: