Is corona going to address this issue … seems odd that we have to do these handstands and swing dead chickens and stuff. Not a bug deal but wasted 30 minutes of my life getting to this point. Combine that by the hundreds that will also attempt to use the TestFlight and the loss of collective life is staggering 
Anyway it would be nice if it was smoothed out.
Yes, we are addressing it. It’s not an easy fix.
Rob
Solving social issues that involve the spinning of chickens and headstands is never easy
Thanks for the update!
While we are waiting for a more solid and vanilla solution I would like to use AirSign to resolve the beta entitlement issue.
I have already tried but did not succeed, but believe I am missing a step.
I import the .ipa I have created with Corona following the above mentioned instructions.
In the AirSign validation section I see that the signature is green.
Then move into the Code Signing section and see a green ball in the Current Signing. In the Re-signing Configuration part of the section I see AppStore-Prepare your app for AppStore selected (I could select other options, but I think this the correct one). However, I can not select anything in Provisioning Profile, which says None. I then changed the name of the app slightly and saved the changes, hoping that by doing so, I would be able to re-sign, but not (?).
More specific/detailed instructions on this part of the process would be very much appreciated.
Think you may be missing the final step … in airsign go to distribution and “save as .ipa”
Had a similar issue till i did that last step.
Use the output of that step to upload to apple
Thanks for the swift answer. I have done that and used the generated .ipa to upload to iTunes using the xCode App Loader.
What I think I am missing is something to do with re-signing. Do we actually re-sign? Do you put anything in the box which says “Provisioning Profile” in Re-signing Configuration? If so, how? Or you just select “AppStore-Prepare your app for AppStore” and move to the next tab -Distribution leaving the “Current Signing” as it is?
In other words. What I am supposed to actually do in the step Code-Signing?
Thanks again.
Jorge
Not exactly sure but i click the “codesign application” on the code signing tab prior to saving the ipa just for good measure … have not tried without doing that … so not really sure if it is necessary or not but … seems like it is working for me. … You could always resort to the hand stands and dead chickens approach but i digress … Happy Holidays.
Thanks Mslack. Your reply made me to progress. I have the wrong directory for air sign to get the provisioning profiles. I can see them now and select the appropriate one (distribution App Store). However, I get a message saying “No valid certificate found for selected provisioning profile”. As a result, the Codesign Application is not active to click (it is grayed). This is unexpected since in the Validation part the “Invalid signature” check is green. Furthermore, I am able to upload the apps to the App Store when I use the .ipa file generated by by AirSign (without "Codesign Application, of course) or even the one coming out straight from Corona. The problem is that the beta entitlement is missing. I have checked the profiles with Apple on the phone a couple of days ago and everything seems ok.
The provisioning profiles appear to be more complex than to build an app!!
Happy Holidays too and a fantastic 2015.
Has anyone got this working with just vanilla Corona?
I’m running into the same issue. Was hoping that anyone has been able to get this working in “vanilla” corona. Have you had any luck? I can see that the beta entitlement is indeed set in my provisioning profile, but it doesn’t seem to be the case in the version that corona is using (or it is just leaving that info out).
I tried using Airsign last night and that didn’t work for me either - will try again later
Gnnehh! Forgot to hit the “codesign” button when using Airsign. Remembering to hit that makes it work.
What is Payload? I just uploaded my app in iTunes Connect and got the error about beta entitlement so I can’t use Test Flight yet. I am following your instructions above and downloaded Air Sign. I have a new app store distribution provisioning profile and my app is built. What is this directory called payload? And are you using AirSign as an alternative to TestFlight? I see TestFlight requires Apple Review (have no idea how long that will take) before your external testers get access to the app.
Payload is just a folder. The .ipa file format basically consists of a zip file made of a compressed folder called Payload containing the .app file. Airsign is a 3rd party codesigning tool. It redoes the signing that Corona does when it builds your project for iOS, but it somehow does something slightly different that supports the Apple Testflight Beta testing.
Here’s the bash script that I use to make .ipa files from the .app file Corona produces when it builds an app.
dir=$(dirname {query}) cd $dir mkdir ./Payload mv {query} ./Payload file=$(basename {query} .app) zip -r $file.ipa ./Payload
{query} is a parameter passed in by Alfred and is the path to the .app file. So usually /User/user/Desktop/MyGame.app. If you replace all the references to {query} with the path to your .app file and run it in Terminal, you should wind up with a .ipa file.
Edit: in fact I think the script can be made Alfred neutral by doing the following:
path="/Users/username/Desktop/MyGame.app" dir=$(dirname $path) cd $dir mkdir ./Payload mv $path ./Payload file=$(basename $path .app) zip -r $file.ipa ./Payload
If you install Airsign, set it up, and then open your .ipa file with it, you can find options to sign the .ipa with the AppStore provisioning profile you were using to build with Corona. Do that, then there’s a button in Airsign marked ‘Save as .ipa’, click that and then upload the new .ipa file made by Airsign using the Application Loader as usual.
Thanks you so much! I’m a newbie so I need a little more detail on where to put this script.
Okay, so I created a folder in my documents called “payload”. Do I open the .app file “show contents in folder” and then put this script somewhere in the .app file and save?
Ah, sorry for the confusion. The script just automates the creation of the .ipa file. You can ignore it if you want. All you need to do is build your Corona project then create a new folder called Payload. Copy your .app file into the Payload folder then compress the folder (right click on it and select compress). Then rename the zip file which doing so will have created to GameName.ipa. You’ll probably need to do this using the Info pane (right click -> get info), and you’ll be asked if you want to change the extension. Click yes and you’ll be ready to get Airsign to sign it for you.
Thank you so very much! Everything worked perfectly and my app is in iTunes Connect now ready for Beta App Review. Hopefully, the review isn’t too long so my external testers can get busy.
Thanks again,
I do the Airsign workaround too. All works fine. Except, when a user downloads the app via Testflight, the download get’s stuck at 90%. The app does install just fine but it’s a little annoying anyway, because most users get back to me and complain about that issue.
Does anybody experience the same behavior? I wonder if it’s Airsign related …
I am still not able to upload apps to the App Store. The beta entitlement continues to be missing. I am now using the “old” TestFlight and it works great. The problem is that I can no longer use their SDK and thus the functinionalities are very limited. Anyway, I can deliver the apps to a number of testers, which makes me happy.
In the meantime, I have realised that Airsign support may not not be their main strenght.
If mail084 or anybodyelse could describe step by step (even clearer than has been described above) what they mean by “Airsign workaround” would certainly help me to migrate to the new TF. I may be doing something (systematically) wrong and can not get out without (your) support.
Here’s another workaround that works for me:
Build your app in corona with a distribution profile.
Create a new folder in the Finder called “payload”. Drop your app in there. Right-Click the folder and and compress it.
Then rename it to “YourAppName.ipa”. This will remove the .zip ending.
Then open that ipa with Airsign. Don’t change anything and don’t resign it. Go straight to the Distribution tab and select. “Export to Organizer”.
Now open xCode go to “Window” and select “Organizer”. Your app should lay in there. From there you can submit it to iTunesConnect. While you do that you can check if it has the beta entitlement. It does for me.
@apps313 I hope that works for you!
@Rob This is quite interesting isn’t it? I can’t submit it directly from Corona. But when I open it once in xCode the beta entitlement works even WITHOUT resigning it in Arising.