Hi @alex,
Once again, thank you for bringing this to our attention!
This should now be fixed with 1.2.9.7.1. Please let us know if this is the case on your end.