Engineering is looking into this. It seems to work sometimes and not at others and we are narrowing in on the missing step. We will update this when we know more.
Rob
Thanks Rob. It seems to be consistently reproduced by simply placing a space in the Application Name.
This is going to be a weird request, but we need this in the bug tracking system to work on it. I know there isn’t a specific “sample” to track the bug, so if you could try and build the hello world sample app, then zip it up as your sample project, include all this information and relevant screens hots then file a bug report using the “Report a bug” link at the top of the page, we would greatly appreciate it.
Please post the bugID number from the email that you receive back here.
Thanks
Rob
I submitted the bug report for this. Case 35827
Any updates on this issue?
I’ve not heard of any updates on this. I know the engineers are aware of problems of spaces in the file names. But the beta entitlement is tied more to certificate type issues if I understand correctly.
Rob
Thanks Rob, is there any ETA on the spaces problem? We’re planning on releasing soon, and I’d rather not submit an app that might have corrupted data in it.
The spaces problem should have been solved in Daily Build 2494.
Rob
Awesome, will try now. Thank you!
So is the signing issue resolved? If so, when can us “basic” users get access to it?
The next public build should have some protections against spaces in file names, folder icons and trying to build to your project folder, all three will generate signing errors. However, there are other things that we can’t protect against like expired certificates, bad profiles and such that can also cause signing errors.
The next public build should be out fairly soon assuming we don’t hit any issues.
Rob
I can confirm that the spaces in app name issue is resolved, but not the beta entitlement issue yet.
I’ll ask where we are with the beta entitlement, but the way engineering was leaning was it’s not a Corona specific issue. It seems to be tied to the certificate. I’ll see if there are any further results from testing.
In the mean time, if you want to delete your keys/certs and profiles and reconstruct them to see if that does the trick. It did in one of the test cases.
Rob
I have the same issue (The beta entitlement issue) 
Please try to fix this asap… 
Thanks
Rob, it must be a Corona issue, because if I use AirSign to re-sign the IPA with the same exact profile I used in the Corona Builder, then the beta entitlement works correctly.
Hi
I up this topic. is there any news regarding the issue.
Does somebody manage to use tetflight with internal testers after a build with Corona?
I tried to regenerate my provisionning profiles, but i still have the warning when i upload a build.
Thks
This is the response I got from corona labs on case 35827
"The advice to refresh your provisioning profiles seems to be good. For us that resulted in the “beta-reports-active” active entitlement being added to the provisioning profile (which must be an AppStore profile, not ad hoc). However, this did not result in the warning going away in iTunes Connect which appears to be an Apple issue.
To confirm that the entitlement is in your app bundle you can unzip the ZIP file created by the build and open the file inside called “embedded.mobileprovision” in a text editor like TextEdit (don’t just double-click it). Search for “Entitlements” and you should see a key called “beta-reports-active” with a value of true. This confirms you’ve regenerated and downloaded things successfully.
If you have a specific setting that you feel should be in your built Corona app to assist with TestFlight please let us know but, as of today, regenerating your profiles seems to be all that is necessary as far as we can tell."
So right now I don’t know what to do. On the other hand the old testflight is working now so I’m using that.
I can confirm the AirSign solution. After resigning with AirSign, I have been able to get beta entitlement to work properly.
Did you get this working? I think I’ve come just as far. I’ve confirmed the beta key is true in the zip submitted to apple. Yet it has a ! warning on the build in iTunes connect and it doesn’t seem to want me to invite test users since the “Internal testers” page for the build only says “Please add users on the builds page…” which I have already done.
I getting really sick of working with app store. Play store was a breeze to set up compared to this mess. :wacko:
Hi, i confirm i am still in the same situation as benny5. Got the beta key in the entitlements re-downloaded from apple, got the internal testers ready and setup properly. Added the build, and enjoying the warning and the missing of the “invite” button. If anybody managed to make this one worked. I did not test the process yet with a native build from xcode.