They pushed out an update late Friday that created this issue. We'll have to wait for them to send out another update to fix it.
View solution in original post
