#27781

We’ve just published a new beta (v360b2), which workarounds the issue. Please give a try.