Doubled Alarms: did I do something wrong?

[IdeaMgr]

Hi folks,

Has anyone else noticed their pre-event alarms doubled on all their
events?

Not sure what happened, or how to clean it up...

Cheers,
-S

(lifetime member of the spanning sync fan club)

[Here in Ky]

Dear S,

I had this happen a few days over the past, say, 10 but just shrugged
it off and now it's gone. I actually don't fully understand how to
control all the little reminders that Google Calendar and iCal want to
send me and since it usually doesn't bug me, I'm fine. But just
thought I would let you know that I, too, received some duplicates
recently.

J

[IdeaMgr]

Thanks J.

I'll wait to see if things just go away!

(or if there's a FAQ on managing alarms)

Cheers
-S

[sigbjod]

Hi,

I have had the same problem with double alarms in iCal. It seems to
happen when I create an event in gcal and when it gets synchronized,
the alarms turns up twice in iCal. One way to only have one
notification is to turn off automatic alarms in gcal: choose a
calender, click on calendar properties, select the messages tab and
disable automatic alarms. To avoid all together unwanted alarms, I
have found no other way than to delete them manually in iCal.

This leads me to what seems to be a bug: an event created in gcal
automatically gets an alarm (10 minutes before, popup message) in
iCal. Does anybody else have this problem? For your information, I'm
using Mac OS X 10.6.1 with Spanning sync 3.0.2.


Sigbjørn

[Byron Shaheen]

Hi,

I'm guessing you all have a default alarm set in the iCal preferences
and when you sync the Google events back to iCal, you're getting the
Google alarm and the default iCal alarm which makes it look like
duplicates. You might want to disable the default alarm in iCal.

Thanks,

Byron

[IdeaMgr]

Thanks Byron... Ill give it a try and let you all know. I did indeed
have a default alarm in iCal.

Is there a better way to set a default alarm? Should I be doing it in
Google calendar?

[Sigbjørn Dybdahl]

Hi Byron,

I was thinking too that it might be the default alarm settings in iCal
that made those double alarms, but the thing is that the default alarm
in iCal is set 15 minutes before the event and my double alarms all
show up 10 minutes before (which is the default setting in gCal).

To explain a bit better my problem, I tried the following use cases
this morning :
1- default alarm in iCal off, default alarm in gCal off :
- an event created in gCal turns up in iCal after synchronization with
a pop-up alarm 10 minutes before the event
- an event created in iCal turns up in gCal after synchronization with
no alarm

2- default alarm in iCal on (15 minutes before, pop-up), default alarm
in gCal off :
- an event created in gCal turns up in iCal after synchronization with
a pop-up alarm 10 minutes before the event
- an event created in iCal turns up in gCal after synchronization with
a pop-up alarm 15 minutes before the event

3- default alarm in iCal off, default alarm in gCal on (10 minutes
before, pop-up) :
- an event created in gCal turns up in iCal after synchronization with
two pop-up alarms 10 minutes before the event
- an event created in iCal turns up in gCal after synchronization with
no alarm

4- default alarm in iCal on (15 minutes before, pop-up), default alarm
in gCal on (10 minutes before, pop-up) :
- an event created in gCal turns up in iCal after synchronization with
two pop-up alarms 10 minutes before the event
- an event created in iCal turns up in gCal after synchronization with
a pop-up alarm 15 minutes before the event

As you see from my tests, the synchronization from gCal to iCal
systematically adds an alarm 10 minutes before the event. Is there a
hidden default alarm setting somewhere?

I have turned on alarm synching in Spanning Sync, but it seems to me
that it only regards synchronization from iCal to gCal. Can anyone
confirm this?


Sigbjørn

[Sigbjørn Dybdahl]

I refresh this thread, as I still have problems syncing alarms between
gCal and iCal using Spanning Sync v 3.0.3. Any input from the spanning
sync crew would be nice.

Thanks,


Sigbjørn