@peach - This app is not wildcarded. I’m trying adhoc dist. cert so that I can uplaod to testflight. I wasn’t aware I could upload a dev cert build to testflight, and if so, would it work on other people’s devices? [import]uid: 11193 topic_id: 11813 reply_id: 110352[/import]
@peach - I just rebuilt using a dev cert instead. Got the exact same error from Test Flight when uploading it:
Invalid IPA: missing embedded provisioning profile. Are you sure this is an ad hoc?
[import]uid: 11193 topic_id: 11813 reply_id: 110357[/import]
testflight’s site says the following about making sure you use an ad hoc dist.
Ensure you are using a Ad Hoc Distribution profile when building and that Xcode is using the correct profile. Building with a Development profile or an App Store Distribution profile will not work.
They also have instructions on making sure there are actual device id’s listed in the embedded.mobileprovision file, which I’v followed, and sure enough, all my device ID’s are listed in there successfully. [import]uid: 11193 topic_id: 11813 reply_id: 110359[/import]
I don’t know - as I said above I don’t use testflight and was simply theorizing on the differences between what people had previously said were successful and to those that were not.
I can only think to re-check and make sure you have followed the same steps yone did above. [import]uid: 52491 topic_id: 11813 reply_id: 110440[/import]
Solved it! - I sent my IPA file to testflight support and they noticed that in the .app file there was a “builds” directory that seemed to have a partial .app file within it. They suggested I remove this.
I do have a builds directory under my app directory that corona is accessing with all my .lua and image/sound files. I always go and delete the previous build files within this folder before doing a new build, but apparently the corona build process actually populates a partial .app file within this directory before it’s finished uploading the whole file structure. So the end result is even if the build directory is empty when the build starts, the final .app file has a partial .app file within it’s build directory when the .app file is created.
So, the fix, is to simply put my builds directory somewhere other than under the actual app structure. Which I did, and following that, my next IPA was accepted by test flight with no errors.
Hope this helps anyone else running into this problem. [import]uid: 11193 topic_id: 11813 reply_id: 110917[/import]
Thank you VERY much for sharing this; this could prove very useful to a number of people. We always warn people not to use a sub folder called “resources” as it interferes with signing but I was entirely unaware of “builds”.
Grats on getting it sorted out, too - very pleased to hear that!
Peach 
[import]uid: 52491 topic_id: 11813 reply_id: 110942[/import]