CODEWITHSUNDEEP
iphoneobjective-cioseventkit
Glenn Barnett
Glenn Barnett

Reputation: 2091

EventKit - App freezes when adding an EKEvent with 2 alarms (iOS 5)

I have an app that programmatically adds reminders to your iOS device's calendar.

Previous to iOS 5, I could add a calendar item with two alarms thusly:

EKEventStore* eventStore = [[EKEventStore alloc] init];
EKEvent* event = [EKEvent eventWithEventStore:eventStore];
// set startDate, endDate, title, location, etc.

[event addAlarm:[EKAlarm alarmWithRelativeOffset:60.0f * -5.0f]]; // 5 min
[event addAlarm:[EKAlarm alarmWithRelativeOffset:60.0f * -15.0f]]; // 15 min

[event setCalendar:[eventStore defaultCalendarForNewEvents]];
NSError* error = nil;
BOOL success = [eventStore saveEvent:event span:EKSpanThisEvent error:&error];

On iOS 5 this freezes the application. It does not return with an error - it just never returns.

If I only call addAlarm once, it works as expected.

On iOS 4.2, calling addAlarm twice works just fine.

Am I doing something wrong?

Upvotes: 5

Views: 2693

Answers (4)

Louie
Louie

Reputation: 5940

Its a bug with Apple. If you set 2 alarms it causes the app to freeze. If you only set 1 it works just fine. This is fixed in iOS 5.1 .

Upvotes: 1

phy
phy

Reputation: 31

I had the same error.

The problem seems that startDate shoudln't be the same as endDate... really silly iOS change!

Upvotes: 0

Jimmy
Jimmy

Reputation: 1

have you tried calling addAlarm using a variable?

EKAlarm *alarm = [EKAlarm alarmWithRelativeOffset:60.0f * -5.0f]]; // 5 min
[event addAlarm:alarm];

EKAlarm *alarm2 = [EKAlarm alarmWithRelativeOffset:60.0f * -15.0f]]; // 15 min
[event addAlarm:alarm2];

Upvotes: 0

ruxy
ruxy

Reputation: 282

If you take a look at the EventKit section in the iOS 5 changes from iOS 4.3 document, it mentions that some items are deprecated for EKEvent. The hierarchy has changed and a new abstract superclass has been added: EKCalendarItem.

Upvotes: 0

Related Questions