Thanks for reporting the issue. I'm testing a new update right now that should include a fix for this bug!
