Hello,

I tested it on version 2.2.3-3 and didn't get the reported error.
I believe it's fixed.
Could you please confirm?

Best regards,
Bruno Naibert.

Reply via email to