Once again, thank you for pointing this out @GM-Mike!
This should now be fixed with 1.3. Please let us know if this is the case on your side.
Thank you.