This was fixed in daily build 2521. It will roll out to Starter and Basic subscribers with our next release. In the mean time using Airsign seems to be the best way to deal with this.
Rob
Nice, really looking forward : )
Oh and that might have been your 11111th post : )
This is quite interesting how genious you all are. Thanks mail084.
Thanks Rob for taking it seriously. I await for the next build (I am a Starter yet) and then will learn how to use it before I jump to the Testers and ask them to set up a new mechanism. Great news, indeed.
I just want to give a thumbs up and say that this solution does work for me to enable Apple to accept beta testing through test flight. This thread should be stickied.
You have to pay for the AirSignApp, specifically after a month. Corona pushes builds every… 3 months? Can we get an ETA on this fix for Basic subscribers?
There is a “beta” build that we released to the public before the Apple 2/1 deadline. You can get it here:
https://developer.coronalabs.com/sites/default/files/CoronaSDK-2015.2545-release.dmg
Rob
I have used this new beta build and I am still having the issue of Apple replying that I am missing the beta entitlement certification and thus I am not able to use TestFlight. All my certificates are brand new and I am sure they have.
Is there any procedure apart from installing the above mentioned beta build and submit an app via Application Loader?
Any other advice?Thanks in advance.
Did you select the distribution profile in the build panel? I once had the ad-hoc selected, which didn’t include the beta-entitlement.
Thanks for the swift reply.
It has worked. Many thanks.Great!
Great! Glad it works!
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.
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.