TestFlight Beta Testing on iTunes Connect - beta entitlement

Solar2D iOS
#61

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.  

#62

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

#63

Nice, really looking forward : )

Oh and that might have been your 11111th post : )

#64

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.

#65

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. 

#66

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?

#67

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

#68

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.

#69

Did you select the distribution profile in the build panel? I once had the ad-hoc selected, which didn’t include the beta-entitlement.  

#70

Thanks for the swift reply.

It has worked. Many thanks.Great!

#71

Great! Glad it works!

#72

No luck. I have tried AirSign and iResign with no luck. All I get is the messages below. I am giving up on this thing and just manually testing using iTunes, then moving on to Unity.

  • External testing is not supported for builds that have been created with a beta version of Xcode or iOS.
  • To use TestFlight Beta Testing, this build must contain the correct beta entitlement. For more information, see the FAQ.
#73

Well, I stand corrected and apologize for the rant.

After even more hours of research and a lot of trial and error, I finally figured out how to use Corona entirely to build and post to TestFlight (leveraging Application Loader, but launched from within), and several other things.

It was painful to get to this point, but we figured it out.

In case anybody is curious, here’s the checklist:

  1. Recreate your App ID to ensure it has the automatically inserted Beta Testing entitlement (not visible, but added).
  2. Generate a provisioning profile for Distribution, not Ad-Hoc. Download it to your machine and double-click on it to install it.
  3. Generate a new certificate.
  4. (NOTE: the 3 things above may not be in order, but get them done however that goes).
  5. Now from Corona, simply build, use your Distribution provisioning profile.
  6. And then when it asks if you want to upload it say yes. No need for iResign or AirSign.

Now on to tackle the next challenge: Game Center… stay tuned :wink:

#74

I would also recommend upgrading to Xcode 7 and Corona release build 2731 when you can. This will remove the “you can’t submit beta builds” error.

Rob

#75

No, it does not remove that error, I am sorry to say :frowning: El Capitan, Xcode 7, latest daily (1731) and I get the same error.

#76

No luck. I have tried AirSign and iResign with no luck. All I get is the messages below. I am giving up on this thing and just manually testing using iTunes, then moving on to Unity.

  • External testing is not supported for builds that have been created with a beta version of Xcode or iOS.
  • To use TestFlight Beta Testing, this build must contain the correct beta entitlement. For more information, see the FAQ.
#77

Well, I stand corrected and apologize for the rant.

After even more hours of research and a lot of trial and error, I finally figured out how to use Corona entirely to build and post to TestFlight (leveraging Application Loader, but launched from within), and several other things.

It was painful to get to this point, but we figured it out.

In case anybody is curious, here’s the checklist:

  1. Recreate your App ID to ensure it has the automatically inserted Beta Testing entitlement (not visible, but added).
  2. Generate a provisioning profile for Distribution, not Ad-Hoc. Download it to your machine and double-click on it to install it.
  3. Generate a new certificate.
  4. (NOTE: the 3 things above may not be in order, but get them done however that goes).
  5. Now from Corona, simply build, use your Distribution provisioning profile.
  6. And then when it asks if you want to upload it say yes. No need for iResign or AirSign.

Now on to tackle the next challenge: Game Center… stay tuned :wink:

#78

I would also recommend upgrading to Xcode 7 and Corona release build 2731 when you can. This will remove the “you can’t submit beta builds” error.

Rob

#79

No, it does not remove that error, I am sorry to say :frowning: El Capitan, Xcode 7, latest daily (1731) and I get the same error.