Guys, this has apparently been updated in the latest version released around Feb 2 or 4.  This was a problem this weekend but it has now been fixed as I just did a quick check.

You may like to verify that it's no longer a problem on your end.