Thanks @daniel2 . @hjy8697 ,
Apologies for the confusion, we have fixed this in version 2.0.1.
Thanks, Tommy