Calendar app raw data shows incorrect date for 2027 DST events

In Apple Calendar, data is stored in an SQLite database. When reading this data through another program, the date/time values of events (calendar items) are read as Unix dates, starting at January 1st 2001 (Unix usually uses 1.1.1970 as starting point).


I have encountered a new problem. When I use the Calendar app in 2026 to add a new calendar item for 2027 some time after the start of daylight savings time in Europe, the date-time-value used is one day before the intended date! (e.g. April 11 instead of April 12). In the Calendar app this is no problem, everything looks fine, but when reading the raw data directly, the date is off. This is regardless of whether it is an all-day event of if it has a specific start and end time.


I tried converting the date-time-value using an sqlite-function (modifier "unixepoch" "31 years") as well as using Java Calendar.add(Calendar.YEAR, 31) – same result.


Am I missing something? Why is Apple Calendar interpreting dates in 2027 DST differently all of a sudden?

Posted on Oct 28, 2026 10:23 AM

Reply
2 replies

Oct 31, 2026 10:37 AM in response to robi_ffm

I may need to apologise, this seems not be an issue with the data stored by Apple Calendar, but of my conversion of it.

Both the conversion method in my SQL driver as well as the conversion in Calendar.setTime() yield deviating results for dates after March 1 2027 (reason unknown to me). A manual calculation of the date and time based on the Integer values from the database now yields the correct and expected values.

Calendar app raw data shows incorrect date for 2027 DST events

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.