Invalid IPA: Keychain-access-group in the embedded.mobileprovision doesn't match your binary.

Solar2D iOS
#1

I am getting this error from TestFlight:

“Invalid IPA: Keychain-access-group in the embedded.mobileprovision doesn’t match your binary.”

And this from XCode when I try to drop my .app onto my device:

_ Invalid signature. _

I recently (a month ago or more) changed my Apple ID email address and everything seems to have been fine since. I do not have the very latest XCode version, but it’s been kept up to date so far.

I have also cleaned and refreshed all the certificates on my machine and iOS developer account, refreshed or recreated the app IDs and provisioning profiles.

As a test, I completely re-requested for a new certificate and created an entirely new app definition all the way through to provisioning profile and yet I still get this problem.

I have googled and found these links which appear to be useful but as I know little about the process they are referring to:

http://www.karlmonaghan.com/2012/08/09/invalid-ipa-the-keychain-access-group-in-the-embedded-mobileprovision-and-your-binary-dont-match/

http://stackoverflow.com/questions/13216659/building-an-ipa-archive-for-testflight-distribution

http://stackoverflow.com/questions/20711248/uploading-a-build-signed-by-an-xcode-bot-to-testflight-rejected-for-get-task-all

AFAIK Corona is handling all the XCode command line work for me and so I cannot change the identity that these posts are referring to.

Can anyone suggest how I can get to building binaries that will install on device again, please?

#2

My problem is fixed. While this may not be everyone’s solution, here’s mine…

Having recreated all my certificates, app id’s and provisioning profiles at least twice, I had been seeing the XCode device install message “No code signature found” and this matched up with posts like this:

http://stackoverflow.com/questions/11971875/ios-app-testing-no-code-signature-found

I started thinking (more, as I’d had suspicions) that the key chain was incorrect, so I took a look at the Corona console output. It said (sorry, I’ve lost the specific message) that two keys were ambiguous and appeared to be noting the same key twice. I opened Keychain Access and sure enough, under Keys there were two keys with the same ID but different expiration dates.

I deleted the older one, rebuilt with Corona and decided to deploy with TestFlight. This time I got no complaints and the app installed just fine.

TL;DR:

After changing my Apple ID email (which is a pain in itself) to continue to build iOS binaries I suspect that I had to refresh all my development certificates, app IDs and provisioning profiles but also clean out my old Keychain keys.

I did not need to clean the project directory as some stackoverflow posts had suggested but that’s probably because Corona will create a new directory for a build every time.

#3

Glad you got it solved.  Thats the first time I had seen that message.  I asked everyone if they had seen it before, but being the weekend, they’ve not had time to respond.  Added to the Rob’s Internal Knowledge base for future reference.

#4

My problem is fixed. While this may not be everyone’s solution, here’s mine…

Having recreated all my certificates, app id’s and provisioning profiles at least twice, I had been seeing the XCode device install message “No code signature found” and this matched up with posts like this:

http://stackoverflow.com/questions/11971875/ios-app-testing-no-code-signature-found

I started thinking (more, as I’d had suspicions) that the key chain was incorrect, so I took a look at the Corona console output. It said (sorry, I’ve lost the specific message) that two keys were ambiguous and appeared to be noting the same key twice. I opened Keychain Access and sure enough, under Keys there were two keys with the same ID but different expiration dates.

I deleted the older one, rebuilt with Corona and decided to deploy with TestFlight. This time I got no complaints and the app installed just fine.

TL;DR:

After changing my Apple ID email (which is a pain in itself) to continue to build iOS binaries I suspect that I had to refresh all my development certificates, app IDs and provisioning profiles but also clean out my old Keychain keys.

I did not need to clean the project directory as some stackoverflow posts had suggested but that’s probably because Corona will create a new directory for a build every time.

#5

Glad you got it solved.  Thats the first time I had seen that message.  I asked everyone if they had seen it before, but being the weekend, they’ve not had time to respond.  Added to the Rob’s Internal Knowledge base for future reference.