Page 1 of 1

Unable to down;oad distribution profiles

Posted: Wed Dec 07, 2011 9:06 am
by SteveHanlan
Not a LC problem, but a problem all the same ...

Running Xcode 4.2 (4C199) with iPhone OS 5.0
I have developer and distribution set up in the iOS provisioning portal with a bunch of devices but when I 'refresh' in xCode, it removes any downloaded distribution profiles and tells me ...

Your team has no devices for which to generate a provisioning profile. Please connect a device to use for development, or manually add a Device ID using the Provisioning Portal.

I can still use the iOS Team Provisioning profile for development and can load the app onto the devices, but I am now unable to get a codesigned app for upload to the store.

Anyone else seeing this kind of problem as a result of upgrading to newer versions of xCode, etc.

cheers

Steve

Re: Unable to down;oad distribution profiles

Posted: Wed Dec 07, 2011 3:16 pm
by Mark
Hi Steve,

Currently, I'm having the same problem. Download the profiles manually and don't click on refresh.

Kind regards,

Mark

Re: Unable to down;oad distribution profiles

Posted: Wed Dec 07, 2011 6:32 pm
by SteveHanlan
Mark

If I do that and use the distribution profile, it compiles ok, but is rejected by iTunes Connect/Application Loader as it does not have a valid codesign!!!!!

Cheers

Steve

Re: Unable to down;oad distribution profiles

Posted: Thu Dec 08, 2011 6:21 pm
by SteveHanlan
Mark.

That works.

I noticed that when I cleaned everything out and logged into the portal as admin (not agent) and did the refresh, it created a .mobileprovision file for a deleted distribution profile and this was where the 'refresh' failed. I clicked off 'automatic' and downloaded one aspect at a time and its all working again.

Phew!

Steve

Re: Unable to down;oad distribution profiles

Posted: Thu Dec 08, 2011 6:31 pm
by Mark
Hi Steve,

I had exactly the same problem some time ago and yesterday again, so I knew that it should work.

Glad to know that you got it working now. I hope Apple will fix this soon.

Best,

Mark