Hi all, plugin author here. As you can see from the alert, the issue was remedied in version 2.0.4, which shipped recently. If you update to the latest version that should be resolved.
Thanks for the nudge! I took a look and was able to put together a fix, which is now available in the latest version of the plugin (2.0.3). Please holler if you continue to have any issues. Thanks!