Recurring events not returned via getEvents()

[jakar]

Starting in either 1.10.2 or 1.10.3 (not sure which), recurring events no longer appear in the results that I get from getEvent(). However, the "ICS: import events" command does still include them.

In case I'm misusing the function (or anything else), here is entirety of my Templater code:

<%*
let icsDateText = tp.file.title?.trim();
icsDateText ??= tp.file.path(true).match(/([^\/\\]+)\.md$/i)?.at(1);
icsDateText ??= tp.date.now("YYYY-MM-DD");
let icsDate = moment(icsDateText, "YYYY-MM-DD");
let icsEvents = await app.plugins.getPlugin('ics').getEvents(icsDate);
icsEvents.sort((a,b) => a.utime - b.utime).forEach((e) => {
	tR += `- \`${e.time}\`-\`${e.endTime}\` — ${e.summary} — *${e.icsName}*\n`
})
-%>

Thanks!

[muness]

Hi @jakar - I wonder if the way you're extracting the date is the issue...

let icsDateText = tp.file.title?.trim();
icsDateText ??= tp.file.path(true).match(/([^\/\\]+)\.md$/i)?.at(1);
icsDateText ??= tp.date.now("YYYY-MM-DD");

That first one might be matching something different altogether. I suggest adding that to the output just to double check what it's resolving to:

tR += ${icsDateText}

[jakar]

Hi @jakar - I wonder if the way you're extracting the date is the issue...

let icsDateText = tp.file.title?.trim();
icsDateText ??= tp.file.path(true).match(/([^\/\\]+)\.md$/i)?.at(1);
icsDateText ??= tp.date.now("YYYY-MM-DD");

That first one might be matching something different altogether. I suggest adding that to the output just to double check what it's resolving to:

tR += ${icsDateText}

Thanks for the quick response. I left out some important context there, sorry. This is being applied to daily notes, where the title is formatted like that. But yeah, that is a little hacky.

Anyhow, adding the debugging line results in this:

2025-09-08
- `18:00`-`19:15` — Redacted non-recurring event — *Redacted Calendar Name*

[muness]

Anyhow, adding the debugging line results in this:

2025-09-08

• 18:00-19:15 — Redacted non-recurring event — Redacted Calendar Name

Using ICS's Get Events you get additional, recurring events?

[jakar]

Anyhow, adding the debugging line results in this:
2025-09-08

• 18:00-19:15 — Redacted non-recurring event — Redacted Calendar Name

Using ICS's Get Events you get additional, recurring events?

Yes, two of them. One all-day event and one additional event with real start and end times. (I just re-verified it right now, for today, as a sanity check.)

[muness]

I don't see a difference in the way you're calling getEvents and the way the plugin in does within Get Events:

https://github.com/cloud-atlas-ai/obsidian-ics/blob/master/src/main.ts#L188-L203

Hmm...

[muness]

Can you try formatting back to text, just in case there's some timezone stuff going with the moment object. i.e.

let icsDate = moment(icsDateText, "YYYY-MM-DD").format("YYYY-MM-DD");
let icsEvents = await app.plugins.getPlugin('ics').getEvents(icsDate);

[jakar]

Can you try formatting back to text, just in case there's some timezone stuff going with the moment object. i.e.

let icsDate = moment(icsDateText, "YYYY-MM-DD").format("YYYY-MM-DD");
let icsEvents = await app.plugins.getPlugin('ics').getEvents(icsDate);

That totally fixed it!

Not sure if it's a timezone issue, because the recurring event happens at 14:45-15:30 local time (right now), which is 18:45-19:30 UTC, so within the same day in either case. But it definitely looks like something with the moment object.

Thanks again!

[muness]

I can't figure out why that fixes it. It's a head scratcher, because that .format("YYYY-MM-DD") should be a no-op as 1.10.3, given:
https://github.com/cloud-atlas-ai/obsidian-ics/blob/master/src/main.ts#L80 calls DateNormalizer.normalizeDateInput which then formats as string:

    // Handle moment objects
    if (moment.isMoment(dateInput)) {
      return dateInput.format('YYYY-MM-DD');
    }

[jakar]

Yeah, that does look pretty straightforward. I don't understand either.

So this is where my javascript knowledge breaks down, but is it possible for there to be two different versions of moment involved here? Some languages allow that, where two versions of a library can coexist (with name mangling happening internally perhaps), but the types and functions from the two are still distinct. So maybe I'm passing a moment version A object and the plugin is checking for a moment version B?

[muness]

So maybe I'm passing a moment version A object and the plugin is checking for a moment version B?

I had the same thought! So I had looked into it and my take is that it's unlikely the cause. moment.isMoment(obj) is duck-typed: it checks obj && obj._isAMomentObject === true, so even different copies of Moment interoperate. Different Moment instances don’t break isMoment, and I'm not using instanceof.

[jakar]

Sorry, I got caught up with other life things and forgot about this.

Anyhow, for what it's worth, the workaround here works perfectly for me. So the question of "is this a real problem?" is now a philosophical one that only you can answer. If you do decide to keep the issue open though, it might be good to summarize or change the title, to help people who discover it in the future.

Thanks again for the help!