This repository has been archived by the owner on Apr 6, 2021. It is now read-only.
Invalid timezone identifier in iCloud feed #24
Comments
|
@steveb85 It might already work! It looks like iCloud uses CalDAV, which broadcasts iCalendar format. Try adding this to your You'll need to replace the Let me know what it says! |
|
@Aupajo thanks, it seems that there is a timezone identifier issue, hopefully this is a simple fix? |
|
@steveb85 Hmm… It looks like the dates are using an unusual or invalid format, which is causing RiCal, the library I'm using to parse iCal feeds, to fail. To fix this, I'll need to understand:
Is there any chance you could send the (scrubbed) output of the feed? Should do the trick. |
|
@Aupajo thanks so much! I've grabbed one event, let me know if this is enough. The data all makes perfect sense to me, and i can't see anything weird, so it has to be the format? Every event follows this same formatting, with the exception of recurring events which add "RRULE:FREQ=YEARLY" for example. |
|
Hmm 🤔 Those values all look fine to me. I'll probably need to look into RiCal's source to dig deeper. I wonder where |
|
at the end of the curl, there is a whole bunch of rules, it looks like to do with daylight savings, but as if it's setting them up for each and every timezone, which would make sense... but they seem to be some odd years, back to 1916 etc (copied below) |
|
In the curl i do get some mentions of other timezones, only on events that were sent from other people in other timezones (i work across multiple, which is why i'm so keen on almanack.... a cross referenced calendar) but they all seem quiet normal. |
|
@steveb85 I'm having trouble reproducing the issue. I created my own iCloud calendar, followed your linked instructions, and it worked for me. Reading the TZInfo::Timezone.get('GMT-0400') # => raises Invalid identifier (TZInfo::InvalidTimezoneIdentifier)So the trick is to figure out where that “GMT-0400” is coming from. Is there any chance you send me the full output of |
|
Thanks! I can do, I’ll just need a couple of days to get onto it, I’ll also try another iCal feed and see if I can narrow it down on my end. |
|
@Aupajo I have also tried new "clean" calendars from ical and it seems to work perfectly, I've been problem solving, and i think perhaps it's to do with the "location" issue you've pointed out as a new issue. I want to test that quickly, otherwise I will send through the full curl |
|
This is a new calendar, and i've only put a handful of events in, but it seems to crash the page. Another calendar that i've manually entered the events in, with no timezone info seems to work fine. This has some that have come from Apps, and have invites attached to it, but i don't see how that should cause a problem |
|
Thanks, @steveb85! I do get an error from this iCal feed: That error I noticed when I was testing this the other day (#26). However, that error is different from the one you mentioned initially: Both of these issues are looking increasingly like issues with RiCal, not Almanack. However, the RiCal project looks dead. I'm going to reach out to the author to see if he will accept a patch to RiCal, and investigate to see if there's some way I can patch this in Almanack if not. |
|
thanks so much @Aupajo that is a huge help! |
|
I sent a message via Twitter yesterday: https://twitter.com/aupajo/status/1128161247701098496?s=20 I haven't heard back, and I'm not sure I will. Moving forward, I'll assume that RiCal is no longer being maintained, and that I'm better off trying to patch this in Almanack. @steveb85 Would you be able to help me isolate the If I can get a iCalendar with the |
|
@Aupajo of course, I'll shoot you a link via email. Steve |
|
@steveb85 I just tried and had no issues parsing the iCal feed you sent in your email. I think I need a bit more information about your system:
Update: Just re-reading your error above, it looks like you're using macOS, with RBEnv running Ruby 2.3.0? Are you running macOS Mojave (10.14)? |
|
@Aupajo Yes running Mojave 10.14.4, last week i changed to Ruby 2.6.3 on RBEnv 1.1.2 |
|
@Aupajo I was reading through the ri_cal documents and found this When RiCal imports an icalendar data stream produced by another library or application, such as It lead me to examine some things more closely, and found that the calendar that was causing the problem had two flights in it, which were registered with a different timezone reference. - They were automatically added, not input by me) when i corrected this, everything started working. thanks for your support on this. |
|
Great! Thanks, @steveb85. I'm glad your issue was resolved. Thank you for reporting it here, too – I can help steer anyone else affected away from it, too. |
|
@Aupajo this popped up again today, after i automatically added some flights to the calendar. The flights came in with TZ indicated in GMT which shouldn't be a problem, however I think the problem is that it left in one time zone and landed in another. I've manually edited it to be both in the same timezone, and will just see if that corrects it. |
|
Interestingly, i had added some events that were over 24 hours, and that didn't seem to be a problem. (all day problem from earlier) |
|
Possible fix for this in #42. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm wondering if we could integrate iCloud as well, using the apple app passwords and the method of finding the calendar URL from here https://www.techrepublic.com/article/how-to-find-your-icloud-calendar-url/ if so it would be a huge help.
The text was updated successfully, but these errors were encountered: