After I upgraded to v1.4.4 from beta the issue is no longer there. I think it is fixed with v1.4.4
1 Like
After I upgraded to v1.4.4 from beta the issue is no longer there. I think it is fixed with v1.4.4