Thanks @joseph_amigo for this discovery. I have fixed the bug in the latest release, v.1.3.4. Please, see this post.