I have also been encountering this problem. I thought it was a mistake I made, but I'm happy to know it's not just me. I believe the error is occurring because of a bug created by the new update, not something you did.