I'm still getting this problem where I create an event on my mac, and it appears as New Event (a default hour long) on my iPhone until I go in and edit it again on the mac.

Now I've also got this problem where if I create an event on my phone, it doesn't update in iCal until I quit the app and relaunch it - a sync doesn't help.

Does it do the same without a jailbreak?

Well it's no good asking *me* that... but it started going wrong as soon as I 'upgraded' to the new mobileme iCal. So it's a combination of that and whatever else.

(If I ever have the several hours necessary to do so, I'll try running it unjailbroken and see if the same issues arise.)

Well, jailbreaking is definitely irrelevant here - the fault is at the mobilecalendar/iCal end: if I create a new event on my mac, it appears in the me.com calendar as a generic New Event; if I create an event on my phone, it has the correct data in mobilecalendar, but displays incorrectly (see image, which shows wrong time in calendar display) and still doesn't reach iCal until I relaunch iCal.

Since the data goes correctly to me.com on its way from the phone, it's clearly not a problem at the phone end - something is screwed up in the exchange between mobileme and iCal.

Hah, turns out the time display bug in mobile calendar is ANOTHER bug - it knows I'm in the London timezone, but doesn't realise our clocks haven't gone back yet, so it's displaying all my events an hour earlier than they should be.

Not just me, then - other folks having similar issues on the mac forum. I'll wait for an update.

Meanwhile, the obvious current workaround is to create all new events in the me.com calendar, which then correctly syncs with the phone and iCal.

Thx for the follow ups.

Apple seems to have fixed this at the me.com end - now events created on phone or mac are pushing correctly to each other.