Closed Aupajo closed 5 years ago
@steveb85 I've fixed the feed URL incorporating :80
and :443
in 1.1.2, which fixes this issue. You can upgrade with:
cd my-almanack-calendar
bundle update almanack
As part of this update, I replaced the webcal://
scheme with the more appropriate http(s) equivalent.
However, I don't believe the presence or absence of port numbers would affect any behaviour in the macOS Calendar app or Google Calendar. Perhaps there's a different issue at play. Does your feed URL start with either http://
or https://
? What steps can I take to recreate your issue?
Any update on this? Even when i pull the port number from the URL Icalendar is throwing an error that stops it from subscribing? Google calendar doesn't throw errors, but doesn't take any of the events.