New Certificate "beta entitlement"?

Solar2D iOS
#1

Hello everyone I’m trying to submit an app to Itunes connect and I want to be able to use new apple testflight application. Currently the old Testflight doesnt seem to be working for IOS8 so I decided to try the new one. I already regenerated my certificates and provisioning profiles but I still get the message “Build 3.1 does not contain the correct beta entitlement. For more information, see the iTunes Connect Developer Guide.”. While doing some research I came across this post on stackoverflow:

"Apple gave us a little surprise yesterday without telling us. There is a new entitlement that is added when you regenerate your distribution certificate. When you regenerate, as others said, it should fix your problem. It’s not due to magic though, it’s because the missing entitlement is now there beta-reports-active = 1

4dNnT.png

Once you download your new provisioning profile, make sure the entitlement is there, rebuild your IPA and this warning should finally go away. If you manage your own Entitlements.plist be sure to include this new key.

<?xml version=“1.0” encoding=“UTF-8”?>
<!DOCTYPE plist PUBLIC “-//Apple//DTD PLIST 1.0//EN” "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version=“1.0”>
<dict>
<key>aps-environment</key>
<string>production</string>
<key>get-task-allow</key>
<false/>
<key>beta-reports-active</key>
<true/>
<key>application-identifer</key>
<string>bkahblahblah</string>
</dict>

</plist> " 

http://stackoverflow.com/questions/25756669/app-does-not-contain-the-correct-beta-entitlement

Since I already tried regenerating my provisioning profiles like 10 times and it still doesn’t work do anyone knows if this is something that is wrong on the Corona sdk side? Maybe when building the app is not including that new “beta entitlement”? I could be wrong but Idk what to do at this point. If Anyone has any information please let me know. 

#2

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

#3

I submitted the bug report for this. Case 35827

#4

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

#5

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. 

#6

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:

#7

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.

#8

I took elpita01s advice and used testflightapp.com instead. I got it to work for my ipad then. Have one tester who hopefully will get going during the week which should confirm.

#9

Yes, no pbs to make it running the old way. Just still waiting to use the testflight app on iOS8.

Will update if i manage to make it work .

#10

Any updates, guys?

#11

hi did not have time yet to check the issue. we still rely on the old testflight way

#12

I took a look at an Xcode build vs Corona build. Apparently two entitlements are missing when looking at the build on iTunes Connect: com.apple.developer.team-identifier and beta-reports-active.

Are you able to use the old Testflight on iOS 8.x?

#13

Got it working on iOS8 by re-signing using AirSign.

Initial requirements:

  • Have a non-wildcard app defined
  • Have a new app store distribution provisioning profile (created after iOS 8 was released)

Steps:

  • Build in Corona
  • Move the app into a directory called Payload 
  • Compress Payload and rename to <yourappname>.ipa
  • Open in AirSign, re-sign and create app for App Store
  • Upload to app store using Application Loader
#14

@yarong

Yes the old testflight way is working on iOS8.

#15

Has anyone been able to get this to work in the new Testflight??

#16

Yes! We got it to work! We followed Yarong’s instructions. We used a non-wildcard identifier although I’m not sure that matters. However, I am sure that the signing must be done via AirSign. We signed with a distribution certificate in Corona and then re-signed with that certificate in AirSign. For some reason Corona signing is not compatible.

Corona: please fix the signing to work with TestFlight!

#17

Oh then it’s definitely something to do with Corona. I’m using the latest daily build too. Anyone from Corona can chime in with info?

#18

I tried and I can confirm that when signing it with AirSign, the warning goes away and the build has the correct entitlements. It’d be great if this was fixed soon.

#19

I would really like to start using this feature as well, hope Corona can fix this.

#20

When I load the app in AirSign, the Validation tab says that it’s a Non-PIE Binary and that it has an Invalid Signature.

I have pinpointed the cause of the problem. This only happens when you enter an Application Name that contains spaces in the Corona Simulator Build Window. It’s inserting a different invalid character that looks like a space instead of a standard space character.

When I load an app that doesn’t have a space in its name, AirSign is not throwing validation errors and everything looks fine. 

I’ve already reported this happening some time ago (Case 36519) but I don’t know if it has been given any attention yet. I think this is a serious problem that should be resolved very soon.

Please fix this!

Thanks.