-
Notifications
You must be signed in to change notification settings - Fork 116
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot sync 2nd calendar from Nextcloud CalDav #492
Comments
I have the same problem. |
Me too |
I'm having the same issue. Both with a Nextcloud CalDav calendar and with a private Google ICS link. |
The same issue with the first private Google Calendar ICS link. The public is working.
Update:
(not sure where it comes exactly from) while later it is used like this: obsidian-full-calendar/src/calendars/parsing/ics.ts Lines 35 to 38 in b5a7986
As a result, on an event with rdate but no rrule it breaks because it's parsed as recurrent but doesn't have rrule property. Hotfix: open compiled plugin code (main.js), find |
Please check that this issue hasn't been reported before.
Expected Behavior
All calendars sync properly from Nextcloud CalDav calendars.
Current behaviour
My main calendar syncs fine, but the second calendar does not sync and gives an error.
JavaScript console output
plugin:obsidian-full-calendar:64715 Revalidation failed with reason: TypeError: Cannot read properties of null (reading 'getFirstValue')
eval @ plugin:obsidian-full-calendar:64715
Steps to reproduce
Calendar information
Nextcloud 25.0.2
Calendar App version 4.4.4
Self hosted instance, all other CalDav syncs work as expected.
Which Operating Systems are you using?
Obsidian Version
1.3.7
Full Calendar Plugin Version
0.10.7
Checks
Possible solution
Not sure why the first calendar is able to sync and this one gives an error. I guess some value is not being fetched properly.
Comments
All other calendar sources work fine except this one, including another calendar from the same CalDav link and other ICS calendars.
The text was updated successfully, but these errors were encountered: