Skip to main content
Inspiring
February 8, 2014
Answered

AIR for iOS Enterprise distribution - how??

  • February 8, 2014
  • 2 replies
  • 4003 views

I want to distribute an AIR for iOS app using my client’s Enterprise Distribution certificate. 

I believe that the app, which I made using Flash CS5.5 and FlashDevelop in Windows, should be compiled using my usual iOS developer’s Ad-Hoc distribution credentials and then, somehow, should be unzipped and re-signed on a Mac. 

Can anyone give a well-written, clear procedure for doing this?

This topic has been closed for replies.
Correct answer Umanoff

Anton, my client's provisioning profile seems to be proper -- it has a 'key' for 'ProvisionsAllDevices' and a value of 'true.' A regular distribution provisioning profile for Ad-hoc dsitribution under a iOS Developers Certificate has a 'key' called 'ProvisionedDevices' followed by an array of permitted UDID numbers.   So this is a good way to tell them apart, no?

Also remember that my problem is how to use my client's credentials to make a usable Enterprise distribution. I don't want to have to get my own Enterprise certificate.

So, assuming that I already have my client's certificate and password and provisioning profile, AND that these are valid files, what steps would I follow?

спаcибо


Well, no thanks to anyone here, I've found the answer. Re-signing is not necessary. The Enterprise distribution is easily done from Flash using valld Enterprise Developer's credentials and the 'Ad-hoc' type of distribution.

Actually, thanks to both of you who TRIED to answer!

cu

2 replies

Participating Frequently
July 9, 2014

Hi,

I have facing the same problem for using the Flash Builder 4.7 (AIR SDK 13) to export the ipa using the enterprise cert. I have using the following cert and export setting, is it correct? please correct me.

--------

Flash Builder 4.7 ActionScript Mobile Project

Enterprise Cert

Have try both Ad Hoc and Final Release Package

MobileProvision is set as "com.xxxxxx.*

AppID is "com.xxxxx.alericmatest"

--------

But when i drag this ipa to ipad using XCode organizer, it will prompt "A valid provisioning profile for this executable was not found".........

Any tips or steps can be share to me?

THX

Ray

User Unknow
Legend
July 9, 2014

There is no difference between exporting IPA with Enterprise or Developer profile. The same files (p12 and *.provisioning).

1) Create ID

2) Create Distribution provisioning file with In House distribution (not Ad Hoc) and link to your certificate from same panel. You must use the same enterprise account

3) Import your p12 private key from keychain to Flash Builder project and link your provisining

4) Generate Final Release package only. Don't use Ad Hoc

Participating Frequently
July 9, 2014

How about the app.xml?? any "special" settings?

User Unknow
Legend
February 8, 2014

I have Enterprise Dev certificates. They provide the same abilities excluding AppStore publishing and udid registering.

You don't need resign anything. Just get your client distribution p12 and provisioning profile that was generated from the same Enterprise account and publish your IPA as usual. But be aware - anyone can install that P12.

P.S. Resigning of third-party ipa is not legal.

UmanoffAuthor
Inspiring
February 9, 2014

I appreciate your answer but it doesn't seem quite right for Windows development. Are you doing AIR for iOS on Windows or a Mac?

We're not talking about re-signing a 'third-party' app. The app is developed by me for a client, and I'm the one who thinks that he has to re-sign, on a Mac, an AIR for iOS app made on Windows.

By the way, I can publish an ipa, on Windows, using my client's Enterprise credentials and using the 'app store' setting in the publish settings. But the app will not then install properly on an iOS device. It starts the installation process, over-the-air, just like any good ad-hoc distribution but at the end of the download the icon just fizzles away.   What does this sound like to you?

thanks, c.u.

Colin Holgate
Inspiring
February 9, 2014

The final App Store build of an app won’t work on any devices, except maybe ones that were test with the Distribution Ad Hoc provisioning.

You could go ahead and submit the app, it may well be ok.