The fix may have been included in the 1.20 patch (are you still having this issue?), but it is not specifically listed in either the 118 or 120 changelists. In any case, there should be another update tomorrow.