[bug] Problem with destroy and create

[sydesb]

Describe the bug

When I use destroy and create on the fly, it ends with an error: Uncaught TypeError: sortable [expando] is null

Here is my goal:

• I have questions that are in several groups.
• A question can change group.
• The order of the groups may change.
• A new group is created if we move a question outside groups that already exist.
• An empty group must disappear.

I made it and everything is fine except when a group is empty of its last question. The empty group is deleted, but the following move crashes everything: "Uncaught TypeError: sortable [expando] is null"

To Reproduce
Steps to reproduce the behavior:

1. Go to https://codepen.io/sylv20/pen/vYxOgVo
2. Click on quest3d to put it in another group. Then, move any question and look at your console (not the console of codepen.io)
3. In your console : "Uncaught TypeError: sortable [expando] is null"

Information

sortablejs = 1.13.0

Reproduction
codesandbox: https://codepen.io/sylv20/pen/vYxOgVo

[MirazMac]

Any updates regarding this? I'm facing the same issue. Basically when I call destroy() on an sortable element and then later call create() on it again, it works mostly fine, but when dragging any element, it would show this error:

sortable.esm.js:1109 Uncaught TypeError: Cannot read property 'options' of null
    at sortable.esm.js:1109
    at Array.some (<anonymous>)
    at _detectNearestEmptySortable (sortable.esm.js:1108)
    at HTMLDocument.nearestEmptyInsertDetectEvent (sortable.esm.js:1186)

[MirazMac]

Any updates regarding this? I'm facing the same issue. Basically when I call destroy() on an sortable element and then later call create() on it again, it works mostly fine, but when dragging any element, it would show this error:

sortable.esm.js:1109 Uncaught TypeError: Cannot read property 'options' of null
    at sortable.esm.js:1109
    at Array.some (<anonymous>)
    at _detectNearestEmptySortable (sortable.esm.js:1108)
    at HTMLDocument.nearestEmptyInsertDetectEvent (sortable.esm.js:1186)

My issue was regarding a MutationObserver I was running, nothing to do with the SortableJS it seems.