Ben

Interesting... thank you for debugging and sharing a working solution. I'm not 100% sure what the issue is based on that snipped due to the encoding, but at a guess...

This is the same issue as #4, it appears to be a long standing issue specifically with Google Calendar's processing of the feed. For whatever reason, it seems to imply...

No specific recommendations, I just use the default Apple ones too. Google Calendar appears to be the only calendar affected, based on user reports of this issue.

Not really sure what else I can do on my side, I'd love someone's input with more knowledge or experience with Google Calendar event generation from a dev perspective. Someone...

On a hunch, I've tried something and it appears to have worked in my testing. I've subscribed to the production one and this new one side by side, and the...

> That said, I am in Central European Summer Time (CEST) as of right now, and the times WOULD be correct for CET (Winter time). Perhaps Summer/Winter timezones are messing...

Damn, okay. Thank you for trying it and reporting back, that was a valuable insight into if this was a valid fix or not. I don't think there is much...

This issue is the worst, and a prime example of [XKCD 927](https://xkcd.com/927/):  Every. Single. Client. appears to handle the 'standard' timezone signature differently. Some of them interpret the lack...

Yeah I had a rather lengthy back and forth with ChatGPT over this, feeding it different examples and trying to get it to generate its own approach and compare. It...

I've just done another test. No matter what, Google Calendar will _always_ set the timezone of the calendar subscription to `(GMT+00:00) Coordinated Universal Time` with the field to change it...