Hello!Thanks for the information, that should be fixed with the next update. I myself also encountered this error today, which means that I could actually fix it.
