Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

TypeError: Cannot read property 'dateTime' of undefined (line 493, file "Helpers") #133

Closed
javedrahman opened this issue Jun 6, 2020 · 5 comments · Fixed by #151
Closed
Labels
bug Something isn't working

Comments

@javedrahman
Copy link

  • Description of the problem - I am getting an error after upgrading to the new version.

  • Screenshots
    image

  • An input ics string that can reproduce the problem

You can see this issue for an example of good information when submitting a bug

@javedrahman javedrahman added the bug Something isn't working label Jun 6, 2020
@jonas0b1011001
Copy link
Collaborator

Seems like a duplicate of #115 , without additional info i can only suggest the same change as mentioned there.

Did the same ics file work with the previous version?

@derekantrican
Copy link
Owner

@javedrahman Any update on this? What version are you running?

@javedrahman
Copy link
Author

Hi. I am on version 5.3. Instead of using the Install method, I have created a timed trigger for startSync to run every 15 minutes. It actually seems to sync just fine but throws the error at the end so overall the script shows as Failed in My Executions.

I think there is an issue with an item in my calendar. because I tried changing the date range for the ICS export and now it does not always fail.

@jonas0b1011001
Copy link
Collaborator

Please try this solution here, this should fix your issue too. Unfortunately that's a common problem in 5.3.

@derekantrican
Copy link
Owner

Seems like this is a duplicate of #135 so I'm going to close it as such

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants