Open GoogleCodeExporter opened 9 years ago
Same issue here; please fix this.
Original comment by MH2...@gmail.com
on 16 Jan 2009 at 6:15
Hi,
is this same error with this?
The server responded with
"HTTP/1.1 409 Can only store an event with a newer DTSTAMP"
Anyone could help?
Original comment by caesar.a...@gmail.com
on 20 Apr 2009 at 11:49
same problem when changing in iCal (OSX) a recurring event "for this instance
only".
on the server remain the old event, in my iCal the new event.
problem when sharing the calendar !
Original comment by bruno.ny...@gmail.com
on 21 May 2009 at 2:07
PS: ok when deleting "this instance only" of a recurring event
+ ok when copying "this instance only" of a recurring event
Original comment by bruno.ny...@gmail.com
on 21 May 2009 at 2:08
Same thing. The worst part is that iCal behaves as if the change was successful
after
the error message closes. (The changes you made appear on the calendar
interface.)
But if you do a command-R to refresh, the changes revert.
Original comment by ironiri...@gmail.com
on 27 May 2009 at 6:37
this issue is driving me crazy!!! the error message i receive when trying to
change a
recurring event is: "HTTP/1.1 409 Can only store an event with a newer DTSTAMP"
it is very frustrating (and makes our calendar system basically useless) that my
google calendar shows the correct information, but other sources (iphone, ical)
show
incorrect information. PLEASE fix this!!
Original comment by breanah...@gmail.com
on 11 Oct 2009 at 5:07
+1 to fixing this please... killing me on snow leopard / iCal.
Original comment by scottshoenfelt@gmail.com
on 16 Oct 2009 at 1:06
Referred from
https://bugzilla.osafoundation.org/show_bug.cgi?id=12377#c5
Original comment by grahampe...@gmail.com
on 19 Nov 2009 at 9:52
+2 - also having this issue on snow leopard / iCal
Original comment by jmcha...@gmail.com
on 30 Nov 2009 at 10:07
I ran into this problem as well in a custom exchange-to-gcal sync script I
wrote (it
uses IMAP to pull from exchange/outlook and caldav to push to gcal). Outlook
apparently does not update the SEQUENCE when modifying the instances of a
recurring
event -- the SEQUENCE always seems to remain set to 0.
Since I wrote the synchronization program I'm using, I was able to work around
the
problem by GET'ing the URI from gcal, checking to see what the stored sequence
number
is, and modifying the about-to-be-pushed icalendar object to have a sequence one
greater (thank you mercutioverona!) before PUT'ing the update.
Obviously for straight-up iCal this workaround have been a non-starter. Out of
curiosity, does iCal do the same thing Outlook seems to be doing and just leave
the
SEQUENCE always set to 0?
Original comment by cliffwoo...@gmail.com
on 1 Dec 2009 at 2:06
You need to be careful when updating SEQUENCE. You are supposed to increase it
only
when you are the ORGANIZER of the event. See RFC5545 3.8.7.4.:
When a calendar component is created, its sequence
number is 0. It is monotonically incremented by the "Organizer's"
CUA each time the "Organizer" makes a significant revision to the
calendar component.
Therefore requiring it to be changed doesn't make much sense to me (since you
will
often be an attendee and in such case you are not allowed to increment it)
Original comment by grepfr...@gmail.com
on 1 Dec 2009 at 5:26
Clearly violating the RFC as a work-around is temporary, but the point stands:
this
issue needs to be resolved on Google's end. It's virtually impossible to
smoothly
update and edit events via CalDAV.
Original comment by ironiri...@gmail.com
on 1 Dec 2009 at 5:31
grepfruit: Actually, Google also won't let me keep the original Organizer; it
fails
with permission denied if any of my icalendar objects actually specify an
organizer
(other than the user I'm posting to gcal as, anyway). So as a further
workaround my
script has to nuke all the organizer fields. Grr.
ironiridis: Agreed 100%.
Original comment by cliffwoo...@gmail.com
on 2 Dec 2009 at 5:57
cliffwoolley: That's issue 38, which Google devs claim to have fixed. Do you
still
experience it?
Original comment by grepfr...@gmail.com
on 2 Dec 2009 at 9:17
I just had this same issue manifest for the first time today, so no, it has not
been
fixed yet.
Original comment by simidchi...@gmail.com
on 11 Dec 2009 at 7:58
simidchieva: grepfruit was talking about issue 38, not this issue.
Original comment by ironiri...@gmail.com
on 11 Dec 2009 at 8:00
Same problem for me. Fix it, fix it fast, please!!!
Original comment by vans...@gmail.com
on 3 Jan 2010 at 10:09
Echoing requests to have this oddity addressed; not sure whether this is a
client issue or a CalDev/Google issue,
so I'll echo this request to the Apple forums -- but, yeah, Google and iCal are
frequently at loggerheads.
Original comment by eemelto...@gmail.com
on 8 Jan 2010 at 3:34
Same problem here - any ideas?
Original comment by mikekju...@gmail.com
on 8 Jan 2010 at 5:16
SAME ISSUES HERE...please fix....
Original comment by eugene.w...@gmail.com
on 19 Jan 2010 at 2:01
I have this same problem when I try to add events to Google Calendar from iCal
that were sent as an .ics file
through e-mail. I double click on the .ics, which opens up iCal. I then
choose my Google calendar as the target.
The event appears to get added, then immediately disappears. I tried adding
the event by mailing it to my gmail
account. Then deleted it and tried the iCal method. That's when I got the
"“HTTP/1.1 409 Can only store an
event with a newer DTSTAMP” error.
Original comment by poshaugh...@gmail.com
on 22 Jan 2010 at 10:46
I am having the same issue. I cannot edit a single instance of a recurring
event.
Original comment by billro...@gmail.com
on 24 Jan 2010 at 2:47
[deleted comment]
Same issue here, on recurring events .
HTTP/1.1 409 Can only store an event with a newer DTSTAMP
Snow Leopard, 10.6.2
Original comment by romain.s...@gmail.com
on 25 Jan 2010 at 9:39
This happens to me too, I'd say about 2 out of 3 times I try to change a
recurring
event. What's the difference in those instances? And is there something I can
do
with this SEQUENCE? I don't know what that is.
Original comment by wallowin...@neo.tamu.edu
on 2 Feb 2010 at 7:19
I was receiving this "HTTP/1.1 409 Can only store an event with a newer DTSTAMP"
error too (when adding an event to the iCal from a Facebook event export).
It was a timezone issue for me. The calendar by default wanted to use GMT, but
when
the event was edited and the timezone updated to my location, it worked and the
event
stayed in my calendar.
Snow Leopard 10.6
Original comment by lkow...@gmail.com
on 6 Feb 2010 at 9:41
I'm getting the same 409 problem
Original comment by laura.ca...@gmail.com
on 23 Feb 2010 at 2:39
Same issue and problem from a few weeks ago.
Really awful. But the weird thing is that with BusyCal I don't find any
problems, but it isn't free so i prefer iCal! :D
Original comment by jujudelg...@gmail.com
on 10 Mar 2010 at 9:30
Still happening, any fix on the horizon?
Running 10.5.8 with iCal 3.0.8
Any recurring event triggers the same message as the original poster mentions,
worse
is that iCal seems to move the event but on refresh it goes back to how it was.
Original comment by willdad...@gmail.com
on 16 Mar 2010 at 6:29
Same issue, seems to be happening much more frequently whenever I add
information to
a recurring event under details or if I try to delete/move it. Sometimes the
changes
go through, sometimes they do not.
Running 10.6.2 with iCal 4.0.1
Original comment by davidfob...@gmail.com
on 30 Mar 2010 at 1:33
I always get this message on recurring appointments when I postpone a reminder
any period of time. It's
consistent and repeatable.
Original comment by floydwhe...@gmail.com
on 4 Apr 2010 at 10:59
Having the same issue when trying to change one instance of a repeated event.
This
is a big problem. Any fix on the horizon?
Running 10.5.8 with iCal 3.0.8.
Original comment by tides...@gmail.com
on 5 Apr 2010 at 6:35
Same issue trying to change one item of a recurrent event. This seems to be
new-- maybe just since updating to
10.6.3?
Original comment by mcooperb...@gmail.com
on 8 Apr 2010 at 4:49
Same issue trying to change one item of a recurrent event. This seems to be
new-- maybe just since updating to
10.6.3?
Original comment by mcooperb...@gmail.com
on 8 Apr 2010 at 4:49
same issue here.
Original comment by cleart...@gmail.com
on 3 May 2010 at 6:20
same issue here
Original comment by tcgacale...@gmail.com
on 3 May 2010 at 10:01
I am also receiving this error when trying to update one instance of a recurring
event while using Mac Mail on Snow Leopard, connecting to a Gmail account using
Google's published recommended client settings.
Original comment by mattmarnell@gmail.com
on 3 May 2010 at 10:20
Original issue reported on code.google.com by
mercutio...@gmail.com
on 19 Sep 2008 at 7:23