Sorry for the delayed reply on this!
We've identified and fixed the issue you reported!

Thanks for the report!