Thank you for your patience on this, @Bear!
This was addressed in 1.3.2 :
Kindly let me know if this is the case on your end.
This should now be fixed with 1.3.3:
Thank you in advance.