Open 0xedward opened 3 years ago
This looks a lot like what I run into with Apple Calendar, except that it doesn't mess up the original event. The error message is The server responded with “500” to operation CalDAVMoveEntityQueueableOperation.
.
Oh hi, past me.
except that it doesn't mess up the original event
Never mind. Choosing "revert to server" often deletes the whole thing. It happens on every second or so operation and is driving me crazy.
Could be related to #109.
Is very likely related to #183
Steps to Reproduce
Other CalDAV Account
in Account Settings on Fantastical 3.3.8calendar
field is CalendarB.Retry
button on the error prompt from Fantastical will fail with the same error.This will block any future EteSync changes from syncing from and to Fantastical. For example, if we create a new event (Event C) on CalendarA. EventC will not show up in CalendarA's journal.
On EteSync side, if we look at the journal for CalendarA after moving EventA from CalendarA to CalendarB. EventA will have its name changed to
Not found
and you will be able to load theRaw
andRevisions
data, but theMain
data will be completely empty. The journal for CalendarB will not contain EventA either.This issue has the same error prompt as this one reported about Google Calendar and Fantastical. Has anyone else ran into this and happens to know a fix for this?