about 3 years
ago -
Ignasi
-
Direct link
Hey there,
We’re aware of this one as @sestus2009 pointed out and a fix for it is already on the way (it’s completed internally, but pending QA verification).
Sorry for the frustration this issue may cause.