Someone else reported that Apple told them the same thing and then managed to fix it himself.

It's ridiculous that Apple claims that they don't know what that means. They have the source code to the application that is emitting that error. I'd suggest looking harder.