This appears to have been fixed in 4.0.2 from their release notes but I have not verified it.