I noticed the same behavior. Looks like a problem with two update mechanisms not recognizing the other.
I noticed the same behavior. Looks like a problem with two update mechanisms not recognizing the other.