Hello @kanesbetas, we just fixed the issue on the version 2.0.2.
Please, let me know if you have any follow ups or questions.