Provisioning Profile not matching Certificate? TestFlight

CoronaCards (Corona in native apps) CoronaCards for iOS / Android
#1

Hi,

I’m having a new issue building a Corona App to be uploaded for TestFlight. The error message is attached. “Get-task-allow values in the embedded mobile provision don’t match your binary. Are you sure you created the IPA with the same type of certificate as the one you used to compile it?”

I have triple checked and tried that the certificate and provisioning profile are for Ad-Hoc distribution. This hasn’t been a problem in the past (a few months ago). I am using a starter license Corona account, someone else is writing the code and I build it. Would having an upgraded account change the .app file that is created with the Corona build? Anyone else having this issue?

Thanks,

Jackson

#2

Same problem here, even though I’ve done it 100 times.

Maybe I messed something up, or it could be a change in the Corona build or TestFlight, as I’m pretty sure I’m building the same way I always have.

#3

I do now wonder if this is a Corona issue. The error message is questioning the certificate for the binary vs the IPA. But the way I create the IPA is with a Corona build on my distribution certificate. I use a payload folder with the app file generated by Corona, zip the folder, and rename to an IPA, which has worked hundreds of times for me.

I don’t change the certificate in creating the IPA so how can the Get-task-allow values in the embedded mobile provision NOT match the binary?

​I wonder if Corona has changed some build stuff in order to work on iOS 8 that’s corrupting builds to be used in TestFlight.

#4

Have you read this blog post?

http://coronalabs.com/blog/2014/09/24/ios-8-and-corona-sdk/

there is a section regarding beta entitlements.

Rob

#5

Hi Jack and Rob,

Good to hear there’s someone else out there with this same problem named Jack. That’s what I’ve been doing too with the IPA file, and the troubleshooting I’ve read leads back to XCode, but I’m not able to change the build settings because it’s Corona code.

Thanks for the link Rob. I’ve tried new provisioning files also. I will look into installing iTunes Connect and seeing if the entitlement is then included with a new provisioning profile.

Jackson

#6

Rob,

But I am using Xcode 5. And I have generated new provisioning profiles. In fact I generated new everything and that still didn’t work.

Public build 2393, all brand new iOS provisioning, Xcode 5, old testFlight (testFlightApp.com) and I get that error. Perhaps code signing to fix iOS 8 broke Xcode 5 builds?

Jack

#7

Jackson,

Perhaps you and I are one of the few holdouts on Xcode 5? I was finishing some major structural changes in my app, using my existing toolset, before getting ready to start testing on iOS 8. Perhaps most everyone else has made the jump? Maybe this is something that broke only for Xcode 5 in the Corona jump to Xcode 6?

Which tools are you using? Which Corona build, which Xcode, etc?

Jack

#8

Jackson, Rob,

I fixed it. 

I’m not in the habit of looking at build logs because if it builds and runs, that’s all we need to know, right?

But with the TestFlightApp issues I decided it was time to look. Buried deep in the compression notices was a message about ambiguous certificates!

Lo and behold, I went into KeyChain Access and yes, there were two. And one I knew I didn’t need. I got rid of it, rebuilt, did my Payload folder thing for TestFlightApp, and it works.

Funny thing is that I had this same extra certificate on Saturday too and I built and uploaded to TestFlightApp no problem. Perhaps that error finally got caught after some Corona code housekeeping when they were doing an iOS 8 fix for the public build.

Anyhow… that worked for me. Either that ambitious certificate was the issue …  or Corona or TestFlightApp happened to fix something.

:wink:  Good luck.

Thanks for your reply also Rob.

#9

Wow, what are the odds we both were confronting the same issue now. Mmm I see must be with the iOS 8 update. I had three certificates, after retrying the rundown a few times. Thanks so much for letting us know how you did it!!

#10

Same problem here, even though I’ve done it 100 times.

Maybe I messed something up, or it could be a change in the Corona build or TestFlight, as I’m pretty sure I’m building the same way I always have.

#11

I do now wonder if this is a Corona issue. The error message is questioning the certificate for the binary vs the IPA. But the way I create the IPA is with a Corona build on my distribution certificate. I use a payload folder with the app file generated by Corona, zip the folder, and rename to an IPA, which has worked hundreds of times for me.

I don’t change the certificate in creating the IPA so how can the Get-task-allow values in the embedded mobile provision NOT match the binary?

​I wonder if Corona has changed some build stuff in order to work on iOS 8 that’s corrupting builds to be used in TestFlight.

#12

Have you read this blog post?

http://coronalabs.com/blog/2014/09/24/ios-8-and-corona-sdk/

there is a section regarding beta entitlements.

Rob

#13

Hi Jack and Rob,

Good to hear there’s someone else out there with this same problem named Jack. That’s what I’ve been doing too with the IPA file, and the troubleshooting I’ve read leads back to XCode, but I’m not able to change the build settings because it’s Corona code.

Thanks for the link Rob. I’ve tried new provisioning files also. I will look into installing iTunes Connect and seeing if the entitlement is then included with a new provisioning profile.

Jackson

#14

Rob,

But I am using Xcode 5. And I have generated new provisioning profiles. In fact I generated new everything and that still didn’t work.

Public build 2393, all brand new iOS provisioning, Xcode 5, old testFlight (testFlightApp.com) and I get that error. Perhaps code signing to fix iOS 8 broke Xcode 5 builds?

Jack

#15

Jackson,

Perhaps you and I are one of the few holdouts on Xcode 5? I was finishing some major structural changes in my app, using my existing toolset, before getting ready to start testing on iOS 8. Perhaps most everyone else has made the jump? Maybe this is something that broke only for Xcode 5 in the Corona jump to Xcode 6?

Which tools are you using? Which Corona build, which Xcode, etc?

Jack

#16

Jackson, Rob,

I fixed it. 

I’m not in the habit of looking at build logs because if it builds and runs, that’s all we need to know, right?

But with the TestFlightApp issues I decided it was time to look. Buried deep in the compression notices was a message about ambiguous certificates!

Lo and behold, I went into KeyChain Access and yes, there were two. And one I knew I didn’t need. I got rid of it, rebuilt, did my Payload folder thing for TestFlightApp, and it works.

Funny thing is that I had this same extra certificate on Saturday too and I built and uploaded to TestFlightApp no problem. Perhaps that error finally got caught after some Corona code housekeeping when they were doing an iOS 8 fix for the public build.

Anyhow… that worked for me. Either that ambitious certificate was the issue …  or Corona or TestFlightApp happened to fix something.

:wink:  Good luck.

Thanks for your reply also Rob.

#17

Wow, what are the odds we both were confronting the same issue now. Mmm I see must be with the iOS 8 update. I had three certificates, after retrying the rundown a few times. Thanks so much for letting us know how you did it!!