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: Jens Miltner <email@hidden>
- Date: Mon, 18 Oct 2010 12:35:43 +0200
Am 15.10.2010 um 16:21 schrieb Fritz Anderson:
> On 15 Oct 2010, at 5:08 AM, Jens Miltner wrote:
>
>> we found that when we just build an iOS app, our enterprise provsioning profile is automatically being embedded into the app (since Xcode 3.2).
>
> Examine the Copy Bundle Resources build phase of the app target in Xcode. Does your provisioning profile appear there? If so, remove it.
>
> Files that get imported to an Xcode project are added to the copy-resources phase unless they appear to be compilable or linkable.
>
> That reminds me… I'd better review the resource phase of my own projects.
>
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?
Thanks,
-jens
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
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