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.
bluebell007
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution