Hi @ssabriel, I’m sorry about this — this issue was reported to us here in v1.0.13, and I’m working on a fix for this right now. I’ll update as soon as I have a fix!