Hi

i just built an App, which i now want to give some people for testing.
I now have a distribution provisioning profile with the 2 other IDs (for iPhone 3G and 4) in it.
The first person with the 3G says that he can load the app into iTunes but as soon as he wants to sync the process stops. The other person (iPhone 4, maybe iOS 5) says that nothing works (after draging the .app folder into iTunes).

I'm not 100% sure if this is supposed to work anyway. So i built the .app folder with corona with the Ad Hoc distribution profile. Than the person loaded the profile from me and the app and dragged both into iTunes. The docs imply that this should work like so, but it is never explicitly stated.

On my device (iPhone 4) everything works fine, but that's maybe because i connected it and Xcode somehow handles this device in a different way.

Any ideas how to get this working?

I'm also confused how to get the .ipa package (this is needed i suppose to upload to iTunes connect, isn't it?), but i only get the .app package from corona..

an .ipa package is just a bit -modified- version of compressed .app folder. To create an ipa package do the following:

1) create a folder named Payload
2) move your application.app into this folder
3) compress (ie create a zip archive) Payload folder
4) change compressed file extension to ipa (ie: application.zip to application.ipa)

Do you know the awesome free service called testflightapp.com? I strongly recommend using it for distributing test builds

http://testflightapp.com

cheers, deniz.

Thanks for help!

Ah, that clearifys it. And yes, i heard about testflight, but i thought it should work that way too (because at the moment i don't have to many testers and i don't need any reporting, so i thought i can just distribute it normally).

So, a few further questions:

• Is the way i described above correct to distribute it for testing?
• Shouldn't it work also with the .app folder and the distribution file or do i really have to make the .ipa? (than the distribution file still has to be downloaded and installed seperately, right?)
• Why is there a need for downloading the provisioning profile anyway? - There is one (embedded.mobileprovision) in the .app folder and in any case the correct provisioning profile could theoretically be placed inside this folder anyway (or is there a reason that they are seperated?)
• To clearify this for me: If I add a device to the provisioning, i have to rebuild the app (i.e use corona to build here)? - Or could i just edit the mobileprovision and distribute it?

Thanks for help