@rwilhoit
FYI, @Miguel released an update today (v2.0.6.0) which includes a fix for this issue.
Feel free to check it out!