New Certificate "beta entitlement"?

Solar2D iOS
#61

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?

#62

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
#63

@yarong

Yes the old testflight way is working on iOS8.

#64

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.

#65

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

#66

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.

#67

No ETA’s.

#68

Any news on this? I am using Air Sign right now… Hoping you guys get it fixed before I have to pay.

#69

The latest daily build 2526 should address the beta entitlement issue.  Please give it a go!

Rob

#70

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.

#71

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

#72

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!

#73

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?

#74

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.

#75

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

#76

The new build solved the problem for me as well.  Thanks!

#77

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.

#78

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

#79

Thanks Rob. It seems to be consistently reproduced by simply placing a space in the Application Name.

#80

I wish i could use this feature. I will update the Corona hopefully it will resolve this issue.