hi,
this is a known bug in v0.18 which is fixed in v0.19, coming very soon…
if you’d rather not wait for the automatic system update, you can apply a manual fix for this described in a previous post here.
apologies for the inconvenience,
richard
hi,
this is a known bug in v0.18 which is fixed in v0.19, coming very soon…
if you’d rather not wait for the automatic system update, you can apply a manual fix for this described in a previous post here.
apologies for the inconvenience,
richard