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