We’ve already received a few reports about this bug and it’s already on our “to fix” list. Unfortunately we still don’t have an ETA that we can share with you at this moment, but rest assured that we are aware of it and that it will eventually get fixed.