Hi @zagency,
Thank you for bringing this to our attention!
This should now be fixed in 1.3.0.1. Please let us know if this is the case on your side.
Thank you.