Hi! We're aware of this bug and have an internal report on it.