Sorry for the late reply, I can't seems to replicate the bug. Does the new update still have this error for you?
