[CLOSED] Uncaught TypeError: Cannot read property 'isSynchronized' of undefined

[miltonfoti]

Sometimes, I'm getting this error when try to expand RowExpander.
It works many times before the error happens.

This is the stack:
Uncaught TypeError: Cannot read property 'isSynchronized' of undefined
at F.removeCls (ext.axd:19)
at F.destroy (ext.axd:19)
at F.destroy (ext.axd:19)
at F.destroy (ext.axd:19)
at Object.destroy (ext.axd:19)
at F.beforeDestroy (ext.axd:19)
at F.callParent (ext.axd:19)
at F.beforeDestroy (ext.axd:404)
at F.callParent (ext.axd:19)
at F.beforeDestroy (ext.axd:1274)

[fabricio.murta]

Hello @miltonfoti!

Are you able to reproduce this problem with the row expander related examples in our Examples Explorer as well? If we can't reproduce the problem in our side, little we can do to help you with the issue. Specially if there are specific aspects being triggered in your use case scenario unbeknownst to us.

[miltonfoti]

FabrÃ*cio,

Sorry, but the samples in Examples Explorer are too simple and does not fit our needs.

We were able to reproduce the error on Examples Explorer, but only if we force the store to reload using Ext.getCmp('grid-1010').getStore().load() and Ext.getCmp('grid-1010').getView().refresh() (when occurs the error) @ http://mvc3.ext.net/GridPanel_RowExp...=1501266086178.

We do need to reload the store because our application have some filters and we are using store with AjaxProxy and StoreParameter. Is that the right approach or are we missing something?

[fabricio.murta]

Hello @miltonfoti!

I tried to reproduce the issue running the two console commands on the example you pointed for no avail. Maybe you could elaborate on the steps to reproduce or maybe derive an example, from that one, where we can clearly reproduce the issue.

I reloaded the store, refreshed the view (translating the commands you provided into their semantics) and then expanded/collapsed rows, and no issue happened. Is that just random, no pattern to reproduce at all?

[fabricio.murta]

Hello @miltonfoti!

I's been some days already and still no feedback from you since our last post. We really want to help but, as pointed before, not being able to reproduce the problem is a real "problem" to get to any solution for you.

We may mark this thread as closed if you don't post any follow-up here for 7+ days from now but, in case you make something by the time it is already marked as closed, you would still be able to post here, and we'll try to help you out on that issue.