topic Quote:JOHN H. (Intel) wrote: in Software Archive

The executable was signed with invalid entitlements

Jorge_R_ — Wed, 17 Jun 2015 16:17:07 GMT

I have an app already published with IntelXDK, now Im updating it and regenerated the certificates and provisioning profiles, the builds is successful but when I try to install the IPA to my device I get the following message:

The executable was signed with invalid entitlements

The entitlements specified in your application’s Code Signing Entitlements file do not match those specified in your provisioning profile. (0xE8008016).

Im not using any plugins, just game center and IAPs, but my certificate was generated with those entitlements, so I dont know what other entitlements the XDK is adding to my app that Im not aware of, I remember when I last published my app I was getting an email warning me that my app uses Push Notifications, but Im not using them and Im not adding any pluggin that uses them. Could it be that Intel XDK is adding them without my knowledge? Then why it says I have extra entitlements?

My device is included in the profiles.

I appreciate any help on this. Thank you

Check if you're device is

John_H_Intel2 — Wed, 17 Jun 2015 18:04:02 GMT

Check if you're device is included in the provisioning profile and that you have the new provisioning profile selected in the XDK Project settings tab.

It is included

Jorge_R_ — Wed, 17 Jun 2015 18:13:00 GMT

It is included.

Not including a device in the provisioning profile raises a different error (“No matching provisioning profile found”)

I see you have a number of

John_H_Intel2 — Wed, 17 Jun 2015 19:21:01 GMT

I see you have a number of provisioning profiles included in your app. Can you remove the ones you are not using, reupload/build and see if that helps?

Also, make sure you are you are using a distribution cert and that you provisioning profiles are not expired.

I included 2 provisioning

Jorge_R_ — Fri, 19 Jun 2015 14:18:42 GMT

I included 2 provisioning profiles in my app, in the Intel XDK tool you have to set 2, one for the Ad-Hoc and the Distribution profiles, only those are the ones I added, they were created from the certificate apple signed from the IntelXDK request. I just created this provisioning profiles so they are not expired.

If the problem were invalid provisioning profiles then the error would say about that because previously I was having that error, after I fixed it and generated new profiles then it started to complain about the "invalid entitlements".

Is there a way for me to know what entitlements the XDK is adding to the app? I don't know why it is adding some entitlements that I did not included.

Is there other way I can ask

Jorge_R_ — Fri, 19 Jun 2015 18:39:50 GMT

Is there other way I can ask for support? Seems that Im not getting many results using this forums.

When you created your

PaulF_IntelCorp — Sat, 20 Jun 2015 01:56:40 GMT

When you created your certificate in the Apple Developer Center did you include "Apple Push Notification service SSL (Production)" with the certificate? This may be the source of that message. Just choose the first option "App Store and Ad Hoc" -- I do not know how you see which of those options was included when you created the certificate.

If the builds are working,

John_H_Intel2 — Mon, 22 Jun 2015 13:27:39 GMT

If the builds are working, then odds are you have valid provisioning profile/cert setup.

Double check that you are not trying to install the PRODUCTION build on your device. You have to toggle to ad hoc before the upload/build. You can not install production builds on your device. They are only for submission to the store.

Quote:JOHN H. (Intel) wrote:

Jorge_R_ — Mon, 22 Jun 2015 22:37:33 GMT

JOHN H. (Intel) wrote:

If the builds are working, then odds are you have valid provisioning profile/cert setup.

Double check that you are not trying to install the PRODUCTION build on your device. You have to toggle to ad hoc before the upload/build. You can not install production builds on your device. They are only for submission to the store.

Thanks, this was the issue, I was building it with the Distribution provisioning profile, I changed to Ad-Hoc and its installing fine now.

Just as a note, previously I didn't have to do that for some reason, I was always using one profile, the same build I installed on my test devices was the one I sent to the store and it got approved. Maybe Ive always been using the Ad-Hoc one and they approved that one??