When sharing archived app via email, why does Xcode attach both the ipa and the mobileprovision?

If you do a checksum on the mobileprovision file inside the IPA and the one outside, you'll notice that they don't match. Your beta users will need the one that is not packaged inside the IPA. I can only speculate on the need for the one inside the app bundle, but perhaps it used in the identification process in conjunction with the one outside.

1 Hmm. If you do Share->Save to Disk... is that IPA different? I do that all the time, and I am able to install the IPA over the air all the time w/out trouble.

The mobileprovision file is of the PKCS#7 format. Good tip that the two are different... – jeff7091 Mar 10 at 6:34 1 The mobileprovision file is only needed once for a particular device. It basically just serves to authorize the device, in the absence of XCode.

Any future IPA files, even for entirely new projects can be deployed to an "authorized" device until the authorization expires, or you replace the provisioning file in XCode. – Barney Mattox Jul 30 at 8:23.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.