I got this on 2/27, checked this forum, and saw that signing out & signing back in fixed the error. I did that and it worked!
