Hi Jim,
We have released a new version 3.0.3 and there we have fixed that issue issue in version 3.0.2.
Thank you!