Thanks! The newly updated version 1.3.0 resolved the bug. If any other issue(s) come(s) up I'll let you know.
