[SOLVED] Could not find certificate for identity & entitlement 'APP ID' has value not permitted by a provisioning profile

As I’m working to debug my In-App Purchase code, I’ve noticed that I get a WARNING on my terminal when it starts building my game. It says:

Corona Simulator[6872:903] WARNING: Could not find certificate for identity (iPhone Developer: Naomi Kokubo (A)) whose user id is: B

The “A” is my iPhone Developer ID I set up before I even knew what I was doing. I’m not sure what “B” is, but it’s another set of 10 digit number/letter. Could it be my account ID assigned by Ansca?

Please note, my problem is not related to this post.

I can complete the build process. I can install the game app to my registered device using Xcode. I can launch the game app on my device. I can play my game on my device. But when I tap to enter In-App Purchase area on my device, Xcode console shows the following Error:

Error: entitlement ‘application-identifier’ has value not permitted by a provisioning profile

I’m guessing that probably because of the above mentioned warning and error, I get stuck “waiting for callback” after store.loadProducts function is called. (If my assumption is incorrect, please let me know. It would be a great help just to know if I’m simply going after a wrong problem.)

Sorry about this long post. Any and all clues and pointers are welcome and appreciated.

BTW, can Ansca change the iPhone Developer ID being used for building my app? From my iPhone Developer ID to Team Admin / Agent’s ID? Some years ago, my partner set up the Apple Developer account for our company, and I inherited it – and I could not change Team Admin / Agent to myself. So I’m stuck having two identities to manage, and my keychain shows: (a) iPhone Distribution identity/certificate of my company (LavaMind), and (b) my partner’s iPhone Developer identity/certificate. My iPhone Developer certificate appears under “Certificates”, but not under “My Certificates”. Can it be the reason why I get the WARNING and the ERROR? If Ansca can somehow change my account setting so that when Corona generates my build, it would use my company’s iPhone Distribution ID (or team agent/admin’s iPhone Developer ID), it might help. I just feel I’ve exhausted all I could to work this one out at this point.

EDIT (SOLUTION):
All I had to do was to make sure I had private/public pair for Team Agent (which is me, the fact which I forgot I worked out when I struggled through cleaning up my keychain a while back). After trying several different approach, I figured out that, when Corona generates device build, it gets the “certificate for identity” from iOS SDK, and iOS SDK / XCode gets the identity from keychain. Because I have separate Team Agent and Team Admin (two separate developers) in my keychain, and one of which wasn’t properly paired, it caused me a lot of confusion.

Anyhow, after private/public pair is installed in my keychain, I see no more Warning and no more Errors. Now, finally, I can start debugging the In-App Purchase routine in my game.

[import]uid: 67217 topic_id: 16201 reply_id: 316201[/import]

FYI, when I generate device build, I’m using my company’s iPhone Distribution Certificate as code signing identity (which is also to be used when I upload the final production build through iTune Connect for approval.)

I intend to uninstall Xcode, remove my iPhone Developer certificate that appears under “Certificates” in my keychain (but keep other Developer Certificate and Distribution Certificate), reinstall latest version of Xcode, and then try again.

Meanwhile, if anyone has any pointer or advice, I’d very much like to hear, even if it’s not a direct solution to my problem. Anything that can help me try something else. I’m sure miscellaneous clues can eventually lead me to a solution… [import]uid: 67217 topic_id: 16201 reply_id: 60467[/import]

Just my two cents.

I was struggling with similar issue, and it had to do with xcode-select set to a different xcode than the latest. [import]uid: 109453 topic_id: 16201 reply_id: 127596[/import]

Just my two cents.

I was struggling with similar issue, and it had to do with xcode-select set to a different xcode than the latest. [import]uid: 109453 topic_id: 16201 reply_id: 127596[/import]