EKEvent eventIdentifier returns null

Question

When I try to get the identifier of an EKEvent, all I get is a nil value. Since in iOS5 EKEvent is a subclass of EKCalendarItem, I figured I might be able to get the EKCalendarItem's UUID, but that returns nil as well.

Every now and then I also get this error while trying to access the identifier or UUID property:

CADObjectGetInlineStringProperty failed fetching uniqueID for EKPersistentEvent with error Error Domain=NSMachErrorDomain Code=268435459 "The operation couldn’t be completed. (Mach error 268435459 - (ipc/send) invalid destination port)"

I've been stuck on this problem for quite some time now, but figured it would be iOS5 beta related. But since we're now at iOS5, it's still not working.

score 9 · Answer 1 · answered Nov 20 '11 at 01:40

9

In my app I found out that if you ask for the eventIdentifier when the eventStore that fetched it has been released, it returns nil. But if you ask for the eventIdentifier before it will return the id ok. You can then release the EKEventStore instance and ask for the identifier with no problem.... Seems that it needs the eventStore to retrieve the id, but I get no warnings.

answered Nov 20 '11 at 01:40

the Reverend

12,305
10
66
121

I get this warning, and I found I was releasing my EKEventStore too soon. Now, I hold it until I'm done with my EKEvents, and everything is fine. I get my data and I have no warnings. – Heath Borders Apr 06 '12 at 20:06
1

This should be part of Apple Documentation. – Dare2Dream Jun 08 '12 at 23:46
This is really problematic in combination with ARC. Thanks for your digging, that would have taken me an undecent amount of time to find. – Steven Kramer Dec 07 '13 at 22:27

score 7 · Answer 2 · answered Nov 04 '11 at 13:15

When I try to get the identifier of an EKEvent, all I get is a nil value

Try to save AND commit your event before retrieving the identifier :

[eventStore saveEvent:event span:EKSpanThisEvent commit:YES error:&err];
NSString *strId = [[NSString alloc] initWithFormat:@"%@", event.eventIdentifier];

score 2 · Answer 3 · answered Feb 28 '14 at 18:33

2

Just going through this problem, turnout the eventIdentifier will be null before commit to database, so you need a commit:YES in the saveEvent function [self.eventStore saveEvent:event span:EKSpanThisEvent commit:YES error:&error];

After that, you can get the eventIdentifier.

My fault was pass a NO to commit: parameter.

answered Feb 28 '14 at 18:33

Jiejing Zhang

1,030
8
16

how i can know that this async process i.e adding event to calendar did finish or the commit process to DB finish ? because i am still getting nil even after trying to access it after the saveEvent Sentence – Zakaria Darwish Aug 19 '15 at 14:24
I through it will be a sync call if add commit:YES parameter, do you use two thread to access the eventIdentifier and save it ? – Jiejing Zhang Aug 20 '15 at 15:09

score 2 · Answer 4 · answered Mar 22 '12 at 15:02

2

eventIdentifier is set when the event is added to the EKEventStore. If you try to access this value before adding it, it would return null.

answered Mar 22 '12 at 15:02

Aditi

99
3

1

how i can know that this async process i.e adding event to calendar did finish or the commit process to DB finish ? because i am still getting nil even after trying to access it after the saveEvent Sentence – Zakaria Darwish Aug 19 '15 at 14:22

score 0 · Answer 5 · answered Dec 27 '16 at 02:24

For me, the eventIdentifier is null because I was not setting the endDate. So generally the eventIdentifier can be null if there are any error on creating that event. You can check for errors like this:

NSError *err = nil;
[store saveEvent:event span:EKSpanThisEvent commit:YES error:&err];
NSLog(@"Error : %@",err);

score 0 · Answer 6 · answered May 19 '17 at 19:15

The EKEvent eventIdendifier isn't generated until the event is saved. You can access/store the eventIdentifier after you've saved the event to the EKEventStore

    [store saveEvent:event span:EKSpanThisEvent error:&err];
    NSString *eventIdentifier = event.eventIdentifier;

score 0 · Answer 7 · answered Aug 22 '17 at 12:38

For Swift 3

I have found out, that the issue was that I have created the store within the function that retrieves the date.

Creating the store outside of the function and using its instance solved the issue.

class CalendarServices: NSObject {

    var store = EKEventStore()

    func fetchEventKitCalendarEvents(date: Date, completion: @escaping (_ events: [EKEvent]?, _ error: Error?)->()) {

        let calendar = Calendar.current

        guard self.getEventKitAuthorizationStatus() == .authorized else {
            completion(nil, CoreServices.setError(message: "AuthorizationStatus != authorized"))
            return
        }

        guard let endDate = calendar.date(byAdding: .day, value: 1, to: date)  else {
            completion(nil, CoreServices.setError(message: "Error creating endDate"))
            return
        }

        CoreServices.background {

            let predicate = self.store.predicateForEvents(withStart: date, end: endDate, calendars: self.fetchEventKitCalendars())

            let events = self.store.events(matching: predicate).sorted() {
                (e1: EKEvent, e2: EKEvent) -> Bool in
                return e1.startDate.compare(e2.startDate) == .orderedAscending
            }

            CoreServices.async {

                completion(events, nil)

            }

        }

    }

}

EKEvent eventIdentifier returns null

7 Answers7

Linked