I know this is strange (or normal in the Apple kingdom?), but I had this happening to me the other day, and I finally figured out that my provisioning profile and bundle name weren't matched. When I changed the bundle name to match, the error went away.