Thanks, I’ve confirmed this bug internally.
Keep an eye on the patch notes section, a fix for this has already been included in 0.7.4b.