@Dom The bug that was reported and has been fixed in here:
, seems to reappear again. For some reason, the changes has been altered somewhere between that day to date. I made a quick test on the latest branch develop, and cherry-picked commit 477e7117 into it. And now, the error seems going away.
If you do have an update on branch develop, I would be happy to test it. Thank you.