Skip to main content
Inspiring
October 6, 2011
Question

Is it proper Ad-hoc distribution process?!

  • October 6, 2011
  • 1 reply
  • 1939 views

I created .key file using openSSL.

I created CSR file using openSSL (windows platform of course)  (as described on adobe website).

I purcahsed developer certificate from apple (99$ yearly).

I installed WWDR intermediate certificate (as shown on apple's website).

Uploaded CSR file and finally received developer certificate.

Converted it into .p12 file (as described on adobe website).

Created new provision profile.

Finally, used .p12 file and .provision profile to build an ipa file for testing.... which worked on my ipad.

I wanted to install the same thing on another ipad, so I took UDID of that ipad.. on apple's website, i added that device.

created distribution certificate (using the exisiting .csr file, did not create it again).

created ad-hoc provision profile using for both ipads.

downloaded and used this new adhoc provision profile and .p12 (existing) to build .ipa file...

it is over 1 hour and still it shows it is building..(i use AIR SDK 3.0, command line, temporary files are showing in the publishing folder)...

usually it takes around 20 minutes to create ipa-test file..

is it normal???? did i do anything wrong?! pls help.

This topic has been closed for replies.

1 reply

October 12, 2011

Hi:

You need not use ad-hoc for the purpose you mentioned. You can just add another device to the existing development profile and redownload it.

Ad-hoc is primarily used to let the steckholders or beta-testers see the "Final" version which will go to appStore. Because AppStore type profiles cant install the app on device and development profile cant go on app store. hence adhoc is the middle of both. (for standard accounts). Also to get features of ad-hoc you must build the ipa-ad-hoc target as it will use the required entitlements.

Inspiring
October 13, 2011

Hi Saumitra,

Thanks for your reply. Actually, there was a problem in my FLA file (particularly in frame 5). When I deleted that frame, it worked (I could publish "Distribution - App Store" ipa-app-store). Obviously, I was trying to publish ad-hoc using ipa-ad-hoc only.. Strange thing (seems a bug) was I could publish ipa-test but no ipa-ad-hoc nor ipa-app-store!!!

October 13, 2011

Yes, this can be a bug. Can you please post the snippet of what exactly you were doing in frame 5? which caused ipa-app-store to stop?