Hi @Marius,
Once again, thank you for bringing this to our attention!
This should now be fixed with 1.3.4.7:
Kindly let me know if this is the case on your end.
Thank you in advance.