Hi,
We are using Bryntum for a long time now, and since 4 months, with the 5.6.0 version of Bryntum we got this error. We don't find a way to reproduce it with one of your example.
We are actually using the 5.6.6 version and still have this issue.
It's seems to happen on the refresh / build of the scheduler. When this crash occurs, the scheduler is left blank, and the only solution is to force refresh the app.
We performed a number of checks on our code to ensure that the component was correctly instantiated.
We'd like to know if you could check from your side if there's a way to prevent this crash.
I will keep trying to find a way to reproduce it, but I hope you can have a look without it.
Thanks in advance.
Have a nice day.
TypeError: Cannot read properties of undefined (reading 'getEventsAssignments')
at get assigned [as assigned] @ https://my-url/static/bryntum-583cce4d.js:30:257544
at get assignments [as assignments] @ https://my-url/static/bryntum-583cce4d.js:216:120253
at get resources [as resources] @ https://my-url/static/bryntum-583cce4d.js:216:115689
at get $linkedResources [as $linkedResources] @ https://my-url/static/bryntum-583cce4d.js:216:118698
at <anonymous> @ https://my-url/static/bryntum-583cce4d.js:225:9530
at Array.forEach @ <anonymous>
at Proxy.onEventStoreChange @ https://my-url/static/bryntum-583cce4d.js:225:9499
at Proxy.onInternalEventStoreChange @ https://my-url/static/bryntum-583cce4d.js:222:62444
at Proxy.onInternalEventStoreChange @ https://my-url/static/bryntum-583cce4d.js:222:75070
at Proxy.trigger @ https://my-url/static/bryntum-583cce4d.js:30:22117