I am not sure if this is the exact same issue, but I was getting the same error. In my organization, every time there is a schema change we deploy...