Hi! Apologies and thanks for the report, would you mind trying again in v0.7.13? I believe we've fixed the issue.
Hmm, after testing this myself it still appears to be an issue. This is our top priority and we'll try to get it fixed ASAP
