Maybe this bug is already fixed in the latest update. If my memory serves me right, I think I ran into the same issue a few weeks ago.
