Many thanks for reporting this & including the error details. I've just released a small update (4.33) that should fix this error.
