I had the same problem, but I have just solved it by re-creating a provisioning profile.

I have just solved it by re-creating a provisioning profile. It's just work-around and I would like to leave it to Xcode though.