2024-12-11 1:00 PM ET - LibCal - Google Calendar Integration Issues - RESOLVED

Springy_Will · 2024-12-11T19:24:10+00:00

There was an error rendering this rich post.

2024-12-11 4:30 PM ET - We have resolved the Google Calendar issues in LibCal. While P12 Keys are working again for the GCal sync, we advise users to move to using the JSON Key Type.

2024-12-11 4:00 PM ET - Our developers may have identified the culprit here, as it's due to a recent update on our end and related to the P12 Authentication Key Types.

2024-12-11 1:00 PM ET - LibCal - All Regions - Intermittent Connection Issues with Google Calendar Sync

We are aware of some issues regarding Google Calendar sync for the Appointments module in LibCal.

Our development is actively looking into this issue, and we'll post updates to this thread when we have them. But if you are experiencing any issues, please comment on this post or submit a ticket to our Support site.

Thank you for being so patient while we resolve this.

Find more posts tagged with

LibCal

Comments

ClaireBowling

Hi Will,

We are experiencing an outage on all our accounts, or at least the five or so I tested.

Claire

aimeegee

Hi, Will,

A student just let me know that she was unable to book an appointment with me at a time that is within my availability. Perhaps this is related?

Thanks,
Aimee

Springy_Will

Hi @aimeegee -

It's def related. You can try to manually create the appointment to see if that works (it's a 50/50 chance to work), or just remove the Google integration temporarily.

Hey @ClaireBowling -

Thanks for letting us know about this! We're still chipping away at this. Hopefully I'll have more news soon!

ClaireBowling

Thanks so much, Will!

Claire

Springy_Will

Hi @aimeegee and @ClaireBowling -

This has been resolved! 🎉

We might have a lead here on what the issue is. Would you be able to confirm that when you configured the Google Integration? Did either of you use a P12 key instead of a JSON one? The issue seems to be related to the P12 keys. We're working on a fix, but creating a new key using a JSON token would be the workaround here.

~~Would y'all be able to test this out? Thank you!~~