New Certificate "beta entitlement"?

Solar2D iOS
#81

Any updates on this issue?

#82

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

#83

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.

#84

The spaces problem should have been solved in Daily Build 2494.

Rob

#85

Awesome, will try now. Thank you!

#86

So is the signing issue resolved? If so, when can us “basic” users get access to it?

#87

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

#88

I can confirm that the spaces in app name issue is resolved, but not the beta entitlement issue yet.

#89

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

#90

I have the same issue (The beta entitlement issue) :frowning:

Please try to fix this asap… :slight_smile:

Thanks

#91

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. 

#92

Any chance this fix could get rolled into the latest public release? That would be extremely helpful.

#93

I can confirm funda nexus 6 that when signing it with AirSign, the warning goes away and funda sony xperia z4 the build has the correct entitlements.

#94

Agreed.  Any forecast on when we can expect this in a public build?

#95

I can confirm the AirSign solution.  After resigning with AirSign, I have been able to get beta entitlement to work properly.

#96

We likely will be doing an interim "beta"build prior to Feb 1, 2015 due to an Apple requirement.  I’m assuming this build will include all fixes up to that point.  We don’t generally provide dates because there are too many variables in play that can cause us to miss a date, but as a guide, public builds are released about every 3.5 - 4.5 months.

Rob 

#97

Any update on the beta entitlement issue?

#98

From what we can tell, all you need to do is create a new set of provisioning profiles.  You may need to regenerate your certificates too.  But when it’s done, you should be able to view your provisioning profile in a text editor (it’s a binary file, but some of its text) and look for:

    <key>beta-reports-active</key>
    <true/>

in the Entitlements section.  This is all part of Apple’s provisioning portal setup from what we can tell.

Rob

#99

Rob, I think we all did the internet search and read the same info you just posted. As far as I know Corona signed builds never make it to TestFlight, however.

I haven’t tried the latest Corona that came out last week. I also haven’t dug too deep into why an AirSigned build works fine and Corona does not. Some diffing may reveal something.

#100

Do you have a case where that key is in the provisioning profile and it fails to upload to testflight?

Rob