The v1.4.4 changelog mentions that this has been fixed.
↧
The v1.4.4 changelog mentions that this has been fixed.