Re: Why does Xcode always embed the provisioning profile in iOS apps?
Re: Why does Xcode always embed the provisioning profile in iOS apps?
- Subject: Re: Why does Xcode always embed the provisioning profile in iOS apps?
- From: Scott Thompson <email@hidden>
- Date: Tue, 19 Oct 2010 07:09:43 -0500
> The provisioning profile is not in the Copy Bundle Resources. The only reference to the provisioning profile is in the Organizer. It's clearly being packaged into the app bundle (and renamed to embedded.mobileprovision) during the first ProcessProductPackaging build step.
>
> From the build log:
> <com.apple.tools.product-pkg-utility> "/Users/jens/Library/MobileDevice/Provisioning Profiles/00E79F9D-8BDB-422E-9FD7-047552BEA888.mobileprovision" -o "/Users/jens/sample apps/Helpdesk/build/Release-iphoneos/Helpdesk.app/embedded.mobileprovision"
>
>
> Any other ideas? Is this the expected behavior?
> Anybody else experiencing the same behavior?
I was under the impression that this was always done as part of the code signing/packaging process.
Nobody should be able to use the provisioning profile without the private key that is associated with it and if you were to pull it out of the application and try to drop it into another application you would be violating the code signature in that other application which would prevent it from being installed anyway.
Scott
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden