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

Event update failed. GMeet and appointment body empty. #1810

Closed
RedRocksAZ opened this issue Feb 27, 2024 · 16 comments
Closed

Event update failed. GMeet and appointment body empty. #1810

RedRocksAZ opened this issue Feb 27, 2024 · 16 comments
Assignees
Labels
bug Something's not working right waiting fix confirmation Hotfix available for testing
Milestone

Comments

@RedRocksAZ
Copy link

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: v2.10.3.0
Edition: Installed / Portable
Sync Direction: G->O

Bug Description
2 messages...Event update failed.
Value cannot be null. Parameter name: input

Also...Google event update failed. Continue with synchronisation.

Steps to Reproduce the Issue

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

Any other information
My Google calendar does get updated. I have attached a screenshot.
OGcalsync.log
OGCS screenshot

📎 Attach your OGcalsync.log file.

@RedRocksAZ RedRocksAZ added the bug Something's not working right label Feb 27, 2024
@Fafner1976
Copy link

#1776

@FilippoLepri
Copy link

#1776

I'm experiencing the same, but I had actually already applied the hotfix ... in fact I am running 2.10.3.1.

It solved at first, but it seems the problem came back.

I guess I am misunderstanding something. :)

@phw198 phw198 added the duplicate Already covered by another issue label Mar 16, 2024
@phw198
Copy link
Owner

phw198 commented Mar 16, 2024

@FilippoLepri Please post evidence (namely your OGcalsync.log file) of the error you are getting under v2.10.3.1

@FilippoLepri
Copy link

@FilippoLepri Please post evidence (namely your OGcalsync.log file) of the error you are getting under v2.10.3.1

OGcalsync.log

I'm very sorry for both:

  • my late reply (terribly busy period)
  • the fact that I can't be more precise (for the same reason as above... I have a few seconds): a little while ago I encountered the same error and it should be included in the file I attach, but now the synchronization seems to end correctly! (Which hasn't happened in WEEKS.)

I hope the attached file will help you better than the poor analysis I can do now.

@BauplanungOberlaustitz
Copy link

Hi @phw198,
I got the same problem with the latest version of OGCS. How can I post my logfile? Upload doesn't work.
Thanks in advance,
Alexander

@paulandersonsco
Copy link

I am having the same issue with 2.10.3.1. It is intermittent. And if I re-sync, it often doesn't re-occur. But I seem, to be getting it at least once per day. Log file from today attached and if you search for 'Value cannot be null' in the logs you will see it from this morning.
OGcalsync.log

@phw198 phw198 self-assigned this Mar 28, 2024
@phw198 phw198 removed the duplicate Already covered by another issue label Mar 28, 2024
@phw198
Copy link
Owner

phw198 commented Mar 28, 2024

Thanks @FilippoLepri @paulandersonsco, looks like this is a different occurrence of the same underlying problem 🙁

📦 This should now be resolved with hotfix v2.10.3.8.zip (see instructions for applying).
      CRCs: Zip = CDC9BA8E Exe = D8AAD363

Please let me know how it goes.

@phw198 phw198 added the waiting fix confirmation Hotfix available for testing label Mar 28, 2024
@phw198 phw198 changed the title Event update failed Event update failed. GMeet and appointment body empty. Mar 28, 2024
@RedRocksAZ
Copy link
Author

RedRocksAZ commented Mar 28, 2024 via email

@phw198
Copy link
Owner

phw198 commented Mar 28, 2024

@RedRocksAZ Your issue was already fixed by #1776 - you weren't hitting the issue fixed under v2.10.3.8 (though this does include both fixes).

@FilippoLepri
Copy link

Thanks @FilippoLepri @paulandersonsco, looks like this is a different occurrence of the same underlying problem 🙁
📦 This should now be resolved with hotfix v2.10.3.8
Please let me know how it goes.

Applied, thank you very much.
The first sync worked, but my problem actually seemed to be not always recurring, so: do you want me to do a specific test?
If you do, let me know exactly what I have to try and I will do it. (Don't hold your breath as I'm terribly busy, but I will do it.)

FL

@phw198
Copy link
Owner

phw198 commented Mar 30, 2024

Thanks @FilippoLepri - I think the steps to reproduce/test the fix are:

  1. Create a new Outlook item with no body/description
  2. Ensure OGCS Settings under Google tab are set to sync Google Meet details
  3. Sync to Google

@phw198
Copy link
Owner

phw198 commented Apr 1, 2024

I'm going to pull this hotfix into the next alpha anyway - I'm pretty confident it fixes the issue, but if you are able to confirm it that would still be appreciated.

@phw198 phw198 closed this as completed in 2b7fe7d Apr 1, 2024
@phw198 phw198 added this to the v2.10.4 milestone Apr 1, 2024
@BauplanungOberlaustitz
Copy link

@phw198 Thank you!

@FilippoLepri
Copy link

  1. Create a new Outlook item with no body/description

01

  1. Ensure OGCS Settings under Google tab are set to sync Google Meet details

Are you referring to the "include meet conferences" option? ... if you are, here it is:
02

  1. Sync to Google

:)
03

Did I do everything right?

FL

@phw198
Copy link
Owner

phw198 commented Apr 2, 2024

Yes, that all looks correct - thanks for confirming @FilippoLepri! 👍🏻

@paulandersonsco
Copy link

Thanks Paul for working on this issue. Apologies for the delayed response, but I was on vacation last week over the Easter break, so only got around to applying the latest release yesterday. All seems to be good so far with no issues occuring. Much appreciated, Paul.

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 waiting fix confirmation Hotfix available for testing
Projects
None yet
Development

No branches or pull requests

6 participants