Enterprise iOS License Distribution...(Solved)

JOHN PATTEN johnpatten at me.com
Thu Apr 17 20:58:21 CEST 2014

Hi All..

In my haphazard way of trouble shooting between phone calls and support emails, etc. etc. I have apparently stumbled across the solution for Enterprise Distribution using Mavericks Server and Profile Manager.

I’m not sure which one of these or the combination was the solution, but thankfully I hadn’t tried some bizarre superstitious act that I would have been forced to recreate every time I wanted to release an Enterprise app :)

Here’s what i (can remember) I did:

1. More meticulous on the naming conventions for the app, the Internal App ID (standalone settings). I made sure they were identical if the name of the app was “TestApp" then Internal App ID was: com.ourapps.TestApp.

2. Double checked that I was using the Enterprise profile.

3. Found my way to TestFlight, and attempted to get it working using that service. Each time I attempted to upload my app it would fail. Fortunately TestFlight provides a bit more info, one line, related to the possible error message. Looking at their support they explained that their system expects your app to be placed in a folder titled, Payload. You then compress that folder rename it, in my case, TestApp.ipa, (I gave it the same name as the app) and then upload that into their system.  Once I did that, my app loaded right up into TestFlight. Mind you, this was after doing steps 1 and 2 above.

I played around with TestFlight, which looks like a nifty way to test apps out with multiple folks, but not a good way to distribute final apps out to your Enterprise staff, and had everything working within TestFlight. Decided to try uploading the same compressed folder, TestApp.ipa to our Apps section in Profile Manager and it worked without a hiccup!

I have since repeated the whole process with a second test app and Profile Manger. It works. My hunch is the naming convention I was using for the Internal App ID and the name of the app was incorrect. They have to be the same. 

As for putting the compiled LiveCode iOS app into a folder titled “Payload,” compressing that folder with the Finder, and then renaming the compressed file <nameofapp>.ipa, ...not sure if that has to be done in that fashion each time or not? I have never seen any documentation from Apple for as to being the case, but it worked for Profile Manager to use the compressed Payload folder.

In any case, happy now and all this ipa work is just making me real thirsty ;)


John Patten

On Apr 16, 2014, at 10:48 PM, Mark Wilcox <m_p_wilcox at yahoo.co.uk> wrote:

> 2. I’m also wondering if there is something special that needs to be done to the iOS app after LiveCode creates the iOS app. The iOS appears to have a app extension and not an ipa extension. Also, I’m guessing the iOS app hast to be compressed before changing the file extension to ipa otherwise it results in just the folder with it’s iOS app components. I hope this makes sense. 
> Bingo! A .app file does not necessarily have the necessary signature but assuming LiveCode was set up properly to build the standalone with your Enterprise distribution profile then it should. Simply compress the .app file with finder and change the extension from .zip to .ipa manually. Then it should work with Profile Manager. I have no idea why LiveCode doesn't finish the job here.
> Mark
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode

More information about the use-livecode mailing list