Thanks a lot for the feedback.
This issue has just been fixed and is now available in version 1.16.2 of the extension. Feel free to update and try again.