This should be fixed next update, thanks for the report!