Hi @gierand,
Thank you for reporting this!
This should now be fixed with 1.3.2.2. Kindly let me know if this is the case on your end.
Thank you in advance.