SignalMQ opened this issue 5 months ago · 1 comments
Should be fixed in 1.3.1, thanks for reporting!