Jump to content

[TOPIC: topicViewTemplate]
[GLOBAL: userSmallPhoto]
Photo

The executable was signed with invalid entitlements. WASTED THREE DAYS SO FAR!
Started by greglosang Dec 05 2014 02:08 AM

5 replies to this topic
[TOPIC CONTROLS]
This topic has been archived. This means that you cannot reply to this topic.
[/TOPIC CONTROLS]
[modOptionsDropdown]
[/modOptionsDropdown]
[reputationFilter]
[TOPIC: post.html]
#1

greglosang

[GLOBAL: userInfoPane.html]
greglosang
  • Enthusiast

  • 34 posts
  • Corona SDK

-------------------------------------------------------------------------------------------------------------------------------------

SOLVED. Please read to save yourself DAYS of time. DON'T TRUST APPLE AUTOMATIC PROVISION PROFILES!

-------------------------------------------------------------------------------------------------------------------------------------

 

I've been a Corona App developer for a couple of years, yet I've still just spent THREE DAYS dealing with some provisioning profiles that recently expired.

 

Long story short, here's where I am now desperate for help.

 

1. I deleted ALL my provisioning profiles and certificates from developer.apple.com

 

2. My device, an iPhone 5 plus, has its UDID entered into developer.apple.com -- this ID has previously worked allowing development builds to be copied to the device

 

2. I've completely reinstalled MAC OS X Mavericks from scratch without restoring anything from backups, so it's  a completely fresh install. I installed all the updates before doing anything else.  Now I have a new fresh machine with nothing restored on it.

 

3. I installed a fresh copy of XCODE

 

4. I installed a fresh copy of CORONA - latest daily build 2014.2515

 

So the keychain is a fresh install of MAC OS X

 

5. I went into XCODE/Preferences/View Details, clicked +, and allowed it to create a new IOS Development Signing Identity. Looking at developer.apple.com, this caused a new provisioning profiles to be created automatically for each one of my Apps, complete with certificates - taking a look at the specific provisioning profile on developer.apple.com that I plan to use, I can see that it includes the 1 and only device I have listed in the devices on developer.apple.com

 

6. Inside the keychain, I can now see the Developer Private Key and Public Key, and the associated Development Certificate -- there's no other duplicates of these items in the keychain

 

7. I build my App with corona using the Development Provisioning Profile with the same id as the App I am building.

 

8. I go into X-Code devices, and right click on my device and choose "Show Provisioning Profiles" -- There's nothing there, so I download the development provisioning profile that corresponding with the App ID I just built from developer.apple.com, then I choose the + on this page, and install that profile to the device. (An iPhone 6 plus in this instance).  Also, here on the devices page, the identifier that shows up with the device on this page matches the UDID number entered into devices on developer.apple.com

 

9. Then I drag the App I just built into the area under the text "Installed Apps" in the devices screen.

 

The message which I have been receiving consistently the last three days is:

 

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.

 

Before I completely wiped out Mavericks and installed it again, I tried every possible thing I could think of for three days, and now that I'm getting this same exact error with a fresh machine and fresh install of everything makes me wonder if I am simply missing an obvious step.

 

How crazy is it that it's THIS difficult just to drag a new App from the computer to a device.  And I've done this already hundreds of times!

 

PLEASE HELP!!!!

 

Let's summarize:

 

Fresh machine, fresh software, new keys, new certificates, new provisioning profile, matches device UDID, profile includes device with correct UDID, build App with this profile, install this profile on device, drag App to device, get this error message. "The executable was signed with invalid entitlements." 



[TOPIC: post.html]
#2

Alex@Panc

[GLOBAL: userInfoPane.html]
Alex@Panc
  • Corona Geek

  • 1,733 posts
  • Corona SDK

Have you tried deleting your provisioning profiles and creating them manually?

[TOPIC: post.html]
#3

j.witczak

[GLOBAL: userInfoPane.html]
j.witczak
  • Observer

  • 12 posts
  • Corona SDK

had you found a solution? I have the same problem.

Thanks for your help :)



[TOPIC: post.html]
#4

Alex@Panc

[GLOBAL: userInfoPane.html]
Alex@Panc
  • Corona Geek

  • 1,733 posts
  • Corona SDK

I'm not sure why his followup comment was removed/deleted, but here it is:


Thanks Alex. I had tried this before I re-installed OS X with no luck. But this time, with your advice I took these steps.



1. I logged my account out of XCODE, so no more of this non-working "automatic" certificate and provisioning profile generation

2. Created the development certificate manually

3. Installed it into keychain manually

4. Dragged it into Library/MobileDevice/Provisioning Profiles manually

5. Installed it onto the phone via X-code devices, manually



It worked!



So while I'm really not sure what was going wrong, I "think" the problem may be that XCODE doesn't automatically install the certificate correctly into the MAC's keychain. That about the only step I'm not sure was happening before.



​But what a colossal WASTE OF TIME thinking Apple was doing this properly and automatically, when it just takes 5 minutes to SHUT OFF APPLE'S AUTOMATION and do it yourself.



Suggestion: Why doesn't Corona explain that iTunes cryptically renames the provisioning profiles when you can instead simply drag the properly named ones in there and shut off this Apple automated mess? Also, it should be more clear that these profiles exist in: Library/MobileDevice/Provisioning Profiles and how to make that directory visible. It would have saved me now four days of wasted time, and would have saved me having to re-install Mavericks for nothing!

[TOPIC: post.html]
#5

j.witczak

[GLOBAL: userInfoPane.html]
j.witczak
  • Observer

  • 12 posts
  • Corona SDK

I'm not sure why his followup comment was removed/deleted, but here it is:


Thanks Alex. I had tried this before I re-installed OS X with no luck. But this time, with your advice I took these steps.



1. I logged my account out of XCODE, so no more of this non-working "automatic" certificate and provisioning profile generation

2. Created the development certificate manually

3. Installed it into keychain manually

4. Dragged it into Library/MobileDevice/Provisioning Profiles manually

5. Installed it onto the phone via X-code devices, manually



It worked!



So while I'm really not sure what was going wrong, I "think" the problem may be that XCODE doesn't automatically install the certificate correctly into the MAC's keychain. That about the only step I'm not sure was happening before.



​But what a colossal WASTE OF TIME thinking Apple was doing this properly and automatically, when it just takes 5 minutes to SHUT OFF APPLE'S AUTOMATION and do it yourself.



Suggestion: Why doesn't Corona explain that iTunes cryptically renames the provisioning profiles when you can instead simply drag the properly named ones in there and shut off this Apple automated mess? Also, it should be more clear that these profiles exist in: Library/MobileDevice/Provisioning Profiles and how to make that directory visible. It would have saved me now four days of wasted time, and would have saved me having to re-install Mavericks for nothing!

I haven't MobileDevice folder in the Library?? Crazy....



[TOPIC: post.html]
#6

j.witczak

[GLOBAL: userInfoPane.html]
j.witczak
  • Observer

  • 12 posts
  • Corona SDK

I haven't MobileDevice folder in the Library?? Crazy....

I founded ;-)




[topic_controls]
[/topic_controls]