Looks like this has been fixed as of 5.0.6
↧
Looks like this has been fixed as of 5.0.6