This issue still exists on the latest version 4.0.7.1
This issue still exists on the latest version 4.0.7.1