This problem exists in version 1.4.0, but not in 1.3.1
This problem exists in version 1.4.0, but not in 1.3.1