We've got this fixed in an update coming soon. Thanks for the report!