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.
jsureke
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