Hi @bear,
Welcome to the community
This was previously an issue in 1.3, but has now been fixed with 1.3.0.1.
Apologies for the inconvenience.
