Thanks for checking. We’ve been able to reproduce here, and this will be fixed in the next update.