Sorry about that! I thought I resolved this, but that wasn't the case. The issue should be fixed now in the update I just pushed out. Thanks for reporting!
