Yes, Rob. The beta key is in the provisioning profile and it fails to be eligible for Beta Testing. Like I said before, I’m signing my Corona build with the same exact provisioning profile as the one I use to re-sign it with AirSign. This makes it clear that the issue is not with the profile, but with how Corona is signing the application. However, I too haven’t tried with the latest daily build since I’m waiting for confirmation that this has been fixed.
Rob, have you been able to upload a Corona build and distribute via TestFlight?
I am having the same issue. Rob, rebuilding certs and profiles and signing certificates and every other potential signifying / identifying document does not help, and takes hours 
So there is another solution needed. I currently have:
<key>beta-reports-active</key>
<true/>
visible in the profile documents.
I know I’m not a PRO user, but I must say that given Beta testing is such an important matter in development and deployment of apps, I do not understand how this is taking now 3 months to resolve.
This needs to get fixed! can corona sdks users not do test flight tests, or even pre releases in general? because if so, I’ve wasted 20+ hours screwing around in iTunes connect and Dev center trying to fix beta entiltments!
This needs to get fixed! can corona sdks users not do test flight tests, or even pre releases in general? because if so, I’ve wasted 20+ hours screwing around in iTunes connect and Dev center trying to fix beta entiltments!
I agree, i have regenerated my provisioning profiles, and have uploaded 6 or 7 versions of my app to iTunes connect. Each time it has the yellow warning triangle in the pre release section, and says i don’t have the right entitlements, and think because of that, i cannot submit my app for a beta app review
I can confirm that you did just waste the time. I have a beta that I am running now that took me a LOT of time to resolve the beta entitlement issues on. Unfortunately, in the process, I lost some of the people that signed up in test flight to test my game. I also had a publisher get frustrated with this, which does not make me look good at all. The worst part is that I really don’t see any indication that this issue is being addresses or even recognized as being an issue.
Things like this are making me consider just switching over to a new environment after 6 games developed in Corona.
So, how did you finally resolve the issues and get a beta test going? This whole thing has slowed my app launch down by a week, I want to know if I should even bother doing a beta test now… Is it even possible?
So I wound up creating my build in Corona and then re-signing the build using a program called AirSign (it’s free for 30 days). There are instructions for this process in this thread but I am more than happy to walk you through it if you’d like.
Are you planning on using Apple’s test flight features? I spent two days getting this to work so I’m happy to share the knowledge.
I recreated all my profiles as well but no luck. It just does’t work.
Yeah. I went through the same thing. It is apparently not the profiles but the way the app is signed. Download and install AirSign and then do the following (assuming that you are attempting to build it using Apple’s TestFlight beta program).
- Build your app with your App Store Profile (in Corona, obviously)
- Create a folder called Payload
- Copy the app into that folder (not the zip file that is generated)
- Compress the Payload folder
- Rename it to YourAppName.ipa
- Open AirSign
- Open that file in AirSign
- In the Code Signing section, select your App Store Distribution from the Distribution Type drop down
- Select your App Store Distribution provisioning profile from the provisioning file drop down
- Press the codesign application button
- Save the file wherever you want
- Upload that version of the app to the app store
Following this process, I was finally able to upload the build to Apple for beta testing.
Good luck!
We need someone to provide us an example app that we can look at. Since the App isn’t that important, Any ole app that has been corona SDK signed that includes a profile that shows the beta entitlement would be helpful for us to look at. You can build your app and use the .zip file from that.
You can then use the “File a bug report” link above.
Rob
I can confirm that using AirSign to sign an app with the exact same provisioning profile that Corona supposedly used when building the app not only fixes the error with the test entitlement, but also the horrible hair-pulling com.corona.template error that shows up when using Application Loader claiming that the app was not signed with the correct certificate. I revoked and rebuilt my certificates and provisions a dozen times with no success, but simply resigning the app with AirSign makes the issue go away completely.
Engineering has found out the difference and will be working to solve it. You can read about it here:
http://coronalabs.com/blog/2014/12/12/using-corona-sdk-with-apples-testflightapp/
Rob
This is great that the issue has been found and is now being worked on.
I have followed the whole process of resigning my apps with AirSign and gotten them to submit. However, AirSIgn is free for a 30 day trial and then costs $10. While I am happy to pay for any software that I need in the development process, it kind of rubs me the wrong way to have to buy something that is the result of a bug in Corona (since I am now past the 30 free period in AirSign).
Is there any indication as to when this issue will be solved and made available as a public release? I am only a lowly starter level subscriber and not a pro or enterprise user and thus have no access to daily builds.
No ETA’s.
Any news on this? I am using Air Sign right now… Hoping you guys get it fixed before I have to pay.
The latest daily build 2526 should address the beta entitlement issue. Please give it a go!
Rob
Hi guys,
I tested this using build 2527 and it working now! I was able to upload my app and I didnt see the message. I was also able to install the app on my phone with no issues.
The new build solved the problem for me as well. Thanks!