This post from just over a week ago reports this and from the GitHub link it appears to have been fixed in the pre-release 1.0.229 but there is not a full release version yet.
1 Like
This post from just over a week ago reports this and from the GitHub link it appears to have been fixed in the pre-release 1.0.229 but there is not a full release version yet.