Error ID: 1624427756

[AndresFBL]

I'm trying to deploy this component in my Experience Cloud Site but I keep recieving the same error (I have aleady give all the permissions asked for in the documentation)

Something went wrong
Try refreshing the page. If that doesn't do the trick, give your Salesforce administrator the following error ID, and describe what you were trying to accomplish.
Error ID: 1624427756
This page has an error. You might just need to refresh it. Error during LWC component connect phase: [Cannot assign to read only property 'handleTimeZoneChange' of object '[object Object]'] Failing descriptor: {markup://cccalendar:ccUpcomingEvents}

Is useful o mention that I have admin profile in the org and the "Calendar for Experience Cloud" works properly

[gtabboud]

I'm not sure, I would advise you to debug the component to see what's causing this.
I am unable to reproduce this error in any of the orgs that I have this code in.

[david-j-park]

I am experiencing the same issue, but have noticed it is only a problem in Aura sites. LWR sites render the component without error.

[gtabboud]

I need a bit more than the details provided here folks. That error doesn't mean much, so if there are errors you're seeing in the browser dev tools, or by debugging elsewhere, would love to get that info since I cannot reproduce this and this code is operating just fine in an Aura site.

[david-j-park]

First off, thanks for looking into this!

The error is on line 32 of ccUpcomingEvents.js, within connectedCallback():

this.handleTimeZoneChange = this.handleTimeZoneChange.bind(this);

In an Aura site with the customer service template in Experience Builder we get the error above indicating that handleTimeZoneChange is a read-only property and can't be changed when dropping it onto the canvas:

In the published site we simply get no events displayed, since the error occurs before the data are loaded.

Looking at the code I'm not clear on the root cause, given that you haven't used the @api annotation on that property, but that's what's happening. Perhaps adding @track on the property would make it explicitly writable? Feels like that shouldn't be necessary, but I'm not sure what else to try.