I’m a new member too, and I’ve come across this error before — it’s already been fixed in the latest version, so updating should resolve it.