Thank you so much for pointing this out - I found the error and have fixed it. This should reflect in the next update. Sorry for that!
