@height8 I think the update just showed the problem up because it required me to log in again.
Searching