Since this post is marked as fixed and I keep encountering this error, I’ve created a new report here: