We will fix it as soon as possible. Thank you for your comment!
The new 1.22 version should fixe this bug!