Hi @chaudes,
Once again, thank you for the report!
This should now be fixed with 1.2.9.9.4. Kindly let me know if this is the case on your end.