Skip to content
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

Multiple Constant Event Update Failed Value cannot be null: Parameter name: input #1803

Closed
BillyJIV opened this issue Feb 14, 2024 · 5 comments
Labels
bug Something's not working right

Comments

@BillyJIV
Copy link

BillyJIV commented Feb 14, 2024

I am on the latest ALPHA release.
image

The issue is reproduceable as it happens every time it syncs multiple times.

My version information is included with the screenshot above.

Sync direction is O>G

image

I have attempted to delete the entries in the Google Calendar and let OGCS recreate it, but doesn't seem to help or work.

help.

Checklist:-

  • Upgrade to the latest release (alpha if available) latest release
  • Reproduce the issue
  • Complete the information below
  • Provide your OGcalsync.log file (see how-to)

OGCS Version: v1.2.3.4
Edition: Installed / Portable
Sync Direction: G->O / O->G / O<->G

Bug Description
A clear and concise description of what the bug is.

Steps to Reproduce the Issue

  1. Go to...
  2. Click on...

Any other information
Any additional information that may help troubleshoot the issue.
📎 Attach your OGcalsync.log file.
OGcalsync.log

@BillyJIV BillyJIV added the bug Something's not working right label Feb 14, 2024
@BillyJIV
Copy link
Author

A clear and concise description of what the bug is.

Everytime the sync occurs multiple errors about value cannot be null displays. Thus I have to fiddle with they sync to get it to complete every day.

@Fafner1976
Copy link

Maybe this could help, looks similar.
#1776

@cece46
Copy link

cece46 commented Feb 14, 2024

In 2.10.3.0 and 2.10.3.1 the bug is present.
In 2.10.0.0 the bug is not present.

@BillyJIV
Copy link
Author

Thank you Fafner1976 for the reference to topic 1776. That hotfix solved my issues as it solved it for those on that thread.

Thank you!

@BillyJIV
Copy link
Author

Issue resolved with hotfix in topic 1776

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something's not working right
Projects
None yet
Development

No branches or pull requests

3 participants