Hello @kurtnybru
Thank you for bringing it to our attention. We will be releasing an update (version 1.2.5) either tomorrow or Saturday and this issue will be fixed.