Distribute in-house - need a little help

You must Login before you can answer or comment on any questions.

I built and deployed an iPad app with Titanium 5 months ago (in-house distribution license). Then this past week I came back to code some fixes and upgrades and had an awful time with the certs and provisioning profiles. So I upgraded to the latest version of Ti and also XCode. After that the errors went away when compiling to an iOS device BUT I think something is still going wong.

A few data points: - I can't find the IPA file after a build. Previously it always got generated. But I see some binaries, they're just not ipa files. - Ti is using my Development profile instead of my Distribution profile. I can't make it use the distribution profile and I thought that's what I needed. - The app ends up appearing in my local iTunes.

I'm afraid I'm getting a "development build" (requiring a registered device) instead of a "distribution build" in which I can install it on any device at my company. How can I fix this? On the "run on iOS device" dialog that pops up when trying to compile to hardware, I have 3 green checkmarks and no errors. But the Provisioning Profile points at my "development" mobileprovision instead of "distribution". Both development and distribution profiles show up as Valid in my xcode. Should I make Ti use the distribution profile? I thought this is what I did before, 5 months ago, when it all worked correctly. But how can I? Ti doesn't seem to let me. Not sure if I'm doing this right. Their UI has changed on this dialog, it's different now. Or if it's correct already, where do I find the IPA? It doesn't seem to be anywhere in the iphoneos tree where I used to find it. Please help.

1 Answer

Accepted Answer

Hi

You have a number of things going on here, I will try my best to help you with them.

I think most of the problems may be how you are compiling the app, are you using the 'compile to device' option which may sound right but it is not the right one for you.

Under the brown parcel icon next to the normal test icon - you can compile for adhoc, here you can specify your ad hoc certificate that you need to have already created, then compile.

From memory adhoc compiles go through the same system as app store distributions, so once you have compiled the app at it looks like nothing has happened - launch Xcode, open organiser from inside and choose archives. Select the app and select 'show in finder' from the menu.

You should then see the app file you are missing.

Hope that helps, if not let me know.

— answered 10 months ago by Malcolm Hollingsworth
answer permalink
2 Comments
  • Malcolm, thanks so much. I had forgotten about the itunes/inhouse compile option, and that's it's different from targeting an iOS device. It's all working and deployed now. Wahoo.

    — commented 10 months ago by ZeroGravPro Developer

  • You are welcome, do not forget to mark it as the suitable answer to help those in the future with a similar problem.

    — commented 10 months ago by Malcolm Hollingsworth

Your Answer

Think you can help? Login to answer this question!