Hello Dennis,
Welcome to the community and thanks for reporting this issue.
As you can see at the top of the stack trace, the problem is not coming from our plugin but from another one. I have fowarded the issue to the project maintainer so I will close this thread.
Thanks again!
Damien