Hey Sam sorry to hear that. I found the error that's causing this and I'll have it fixed by v0.32.3
And thanks for the detailed info on the bug!
