Missing or invalid signature. Not signed using an Apple submission ticket.

I found similar posts and tried everything, just seeing if it’s something with Corona, Apple, Certificates, or Profiles.

I developed an app for a client, she gave me her Apple developer username and password to take care of everything for her. When I publish it out in Corona, I can neither test on my device using the Developer profile or upload to iTunesConnect via Application Loader using the Distribution profile.

Corona SDK: 2015.2534
Application Loader 3.0

Xcode: 6.1.1

1.) I cleared all previous profiles in Terminal:

cd ~/Library/MobileDevice/Provisioning\ Profiles

rm *.mobileprovision

 

2.) Created a new Certificate in Keychain Access using my client’s name and email address.

 

3.) Created iOS Developer and a Distribution Certificates in developer.apple.com using said Certificate

 

4.) Created an App ID

 

5.) Added the UDIDs of my iPad and her iPad

 

6.) Created iOS Development and iOS Distribution Provision Profiles using the corresponding Certificates

 

7.) Downloaded and double-clicked on the profiles to open Xcode

8.) Xcode Preferences: Added client’s Apple ID and Password; Details show correct Signing Identities and Profiles

9.) Created App Profile on iTunesConnect using the App ID

10.) Opened project in Corona SDK and published for iOS

       - Publishing using Developer certificate doesn’t allow me to drag/drop/sync it to my iPad via iTunes, it never installs correctly

       - Publishing using Distribution certificate asks me to Upload to App Store

11.) Using Application Loader 3.0, I get the error mentioned in the title

12.) Tried using an app name with and without a space between words, didn’t make a difference.

I feel like I’ve covered every step, but I haven’t developed any iOS apps yet, so I might be missing crucial steps.

Just for reference here is my build.settings file. It’s an iPad-only app.

-- build.settings settings =  {       orientation =       {           default = "landscapeRight",           supported = { "landscapeLeft", "landscapeRight" }        },        iphone =         {            plist=            {               CFBundleShortVersionString="1.0",               CFBundleIdentifier="com.bigcityanimals.bostonbernie",                 UIApplicationExitsOnSuspend = false,                 UIStatusBarHidden = true,                 CFBundleIconFile="Icon.png",                 CFBundleIconFiles = {                      "Icon.png",                      "Icon@2x.png",                      "Icon-72.png",                      "Icon-72@2x.png",                      "Icon-76.png",                      "Icon-76@2x.png",                      "Icon-120.png",                      "Icon-60.png",                      "Icon-60@2x.png",                      "Icon-Small-50@2x.png",                      "Icon-Small-50.png",                      "Icon-Small.png",                      "Icon-Small@2x.png",                },          UILaunchImages = {                     { -- iPad LandscapeLeft                          ["UILaunchImageMinimumOSVersion"] = "7.0",                         ["UILaunchImageName"] = "Default-Landscape",                         ["UILaunchImageOrientation"] = "LandscapeLeft",                         ["UILaunchImageSize"] = "{768, 1024}"                       },                     { -- iPad LandscapeRight                          ["UILaunchImageMinimumOSVersion"] = "7.0",                         ["UILaunchImageName"] = "Default-Landscape",                         ["UILaunchImageOrientation"] = "LandscapeRight",                         ["UILaunchImageSize"] = "{768, 1024}"                       },                  },               },          },   }

Just for good measure, I followed this forum post and installed AirSign and tried re-signing the app using that, but nothing. AirSign shows all green checkmarks, but Application Loader rejects all the .ipas I make with the Distribution Certificate and the Scan code it generates to install the app on a device give an error saying ti can’t be installed.

I even reinstalled all of Apple’s .cer files just in case and that didn’t help. Revoked all certificates, app ID, profiles, etc. and did a fresh start and nothing. Just had to submit a tech support ticket to Apple to see if they can help. Hopefully it’s not on Corona’s end and they just point the finger.

GP,

I’ve found that Apple absolutely will not support anything that isn’t built with their tools. As soon as I mention Corona to anybody at Apple, their immediate response is “We can’t support third party applications”. Let me know if they actually do help you.

Thanks --Charlie

Hi Greg,

This kind of thing happens even to the best of us, and very likely you’re missing one tiny step somewhere along the way. Before trying to install the app on your device(s), did you sync it up, then check in Xcode that the profiles are installed on that device with no errors?

I assume you’ve seen (and followed with extreme care) our iOS Distribution guide:

http://docs.coronalabs.com/guide/distribution/iOSBuild/index.html

Also, try removing the “CFBundleIdentifier=“com.bigcityanimals.bostonbernie”,” key from your build settings. I don’t think that’s necessary.

Brent

Hey Brent,

I went through every step numerous time for the past couple days and tried different varieties of build.settings, icons, profiles, certificates, etc. I have a .zip folder of the exported project and screenshots of every step if you think it’d help.

It should also be noted that when I use a Development certificate to install the app on my iPad via Xcode > Devices > + I get the error “App installation failed. The application does not have a valid signature.”

I tried this with both my client’s developer profile and mine. Both of our accounts show up in Xcode > Preferences and all corresponding certificates and profiles appear under our accounts.

Hi Greg,

I’m looking at your source files and screenshots (sent to me by another Corona staff member). Things appear OK, but these issues are always tricky.

  1. Can you remove that key-value pair that I suggest and try again?

  2. I assume from the Xcode “Preferences > Accounts > View Details…” window, you clicked on the little “refresh” button in the lower-left corner? Then, you synched up your device, restarted the Corona Simulator, and tried to re-build using the proper profile?

  3. Can you show me a screenshot from the Xcode “Devices” window (Command-Shift-2), where you right-click the device (when it’s connected via its cable) and select “Show Provisioning Profiles…” ?

Brent

Just as an FYI, we made changes to the code signing before the most recent public release that fixes a ton of these signing issues.  I know Greg posted that he’s using a recent daily build, but Charlie, what version of Corona are you using?  Greg’s case is different, he’s trying to use someone else’s credentials along side his own.

Rob

In Xcode, I right-clicked on my iPad and deleted every provisioning profile that isn’t my client’s development one. I also went into preferences and deleted my account, only leaving her account, which shows her development and distribution signing identities and profiles.

I then published out the app in Corona’s daily build from yesterday using her development certificate, and in Xcode added the app to my iPad, which gave the error: App Installation Failed. The application does not have a valid signature.

I was hoping getting rid of my account in preferences and all my profiles would help.

You may need to go into Keychain Access and remove every developer related key and certificate and then just add hers back in.  I noticed that the names on her development and distribution certificates are different too.  I don’t know if that will cause an issue or not.  Does she have two different accounts with Apple?  Did she generate her key/cert pairs differently?  Can she build an app for the store (doesn’t have to be Corona an Xcode sample app would work too)?

Do you have access to her provisioning portal?  You could revoke her keys (if she’s not doing any development herself) and build them yourself using her developer login and make sure that process is accurate.

Rob

Also, have you looked in the console log for additional errors?  I was having issues last night trying to use Xcode to install a known good provisioning profile and it was giving me an error about entitlements not matching.   Comes to find out after downloading a new profile to make sure all entitlements were there, a look at the console reveled a different message.  My device wasn’t in the profile (which it was not, so much for a known good profile…), but the only reason I knew the exact cause was because I found more info in the console log.

Rob

You may need to go into Keychain Access and remove every developer related key and certificate and then just add hers back in.
I tried this before, but am going to do it again. Go to do a fresh start: part 7

I noticed that the names on her development and distribution certificates are different too.  I don’t know if that will cause an issue or not.
I was  concerned about this, too. However, when I create a certificate request in Keychain Access and add them to developer.apple.com to create the Dist and Dev profiles, those are the names that automatically appear. I can’t change that.

Does she have two different accounts with Apple?
That’s just what shows up in her developer account.

Did she generate her key/cert pairs differently?

I’m actually the one in charge of all the tech work, I have full access to her account and am making the key/cert pairs the same.

Can she build an app for the store (doesn’t have to be Corona an Xcode sample app would work too)?

I can’t get a build with the Dist profile to uploader via Application Loader 

 

Do you have access to her provisioning portal?  You could revoke her keys (if she’s not doing any development herself) and build them yourself using her developer login and make sure that process is accurate.

I’ve revoked all her stuff a few times to do fresh starts.

Here is what I tried just now:

1.) Deleted my certificates and her certificates from Keychain Access. Revoked/deleted her certificates, App ID, and profiles from developer.apple.com. Deleted all provisioning profiles from my iPad and computer. Deleted my account from Xcode Preferences. (i.e. Fresh Start)

2.) Created a certificate signing request using her name, generated a new Development Certificate using that.

3.) Created a certificate using her company name (which has been showing up as the name on the Distribution certificate anyway) and used that to create a Distribution certificate. Installed those certificates so they appear in Keychain Access.

4.) Generated a new App ID and Distribution and Development Profiles, Downloaded them, imported them onto my iPad via Xcode and refresh her profile in Xcode Preferences to make them appear under her account.

5.) Published the app using her Development profile in Corona SDK.

6.) In Xcode, added the app to my iPad, got an error saying it doesn’t have a valid signature.

7.) In Corona SDK, published the app using the Distribution Certificate, tried to upload via Application Loader 3.0.

8.) Received new error: ERROR ITMS-90034 "Missing or invalid signature…not signed using Apple submission certificate."

9.) Here is what I get on my iPad in Xcode when trying to install the developer version of the app. http://www.ganimations.com/consoleLog.txt

More interesting news…

I deleted my client’s certificates/profiles/appID/etc. from my computer and iPad.

I downloaded and installed my certificates, profiles, etc. on my MacBook and iPad and published out an app that is already on the App Store in Corona SDK using the developer certificate, which is also installed on my iPad via Xcode.

I get the same error  App Installation Failed. The application does not have a valid signature.

Just to be sure it isn’t my iPad or the fact that the app was made using Kwik, I also tried installing another iOS iPhone app on my iPhone 5, which is also already on the App Store and get the same error.  App Installation Failed. The application does not have a valid signature.

Well, thanks to Charles McKeever, I figured it out…kind of.

It turns out the errors are related to my computer. If I create the certificate signing request on my computer, make the profiles/certificate/app ID, etc. on there, and publish out in Corona I get nothing but errors.

If Charles creates the signing requests on his machine, no problems at all for testing or distribution.

If I create it on my wife’s computer, it works fine as well.

So on my MacBook, I uninstalled Xcode, reinstalled Xcode, restarted my computer, cleared all Keychain certificates, cleared all provisioning profiles from Mac and iPad, repaired Keychain Access and it still gives errors. Looks like for whatever reason, I have to publish the apps on my wife’s MacBook.

Rob,

I’m using version 2014.2511

Last I looked, that was the latest version. Let me know if there’s a newer version and how I can get it (I use the free starter version).

Also, similar to the woman that GP is doing work for, my development account and my distribution account have different names with Apple. I’ve read that this can be a problem. Do you think that has something to do with my inability to publish?

Thanks

Charlie, I was just able to publish this even though the names are different. I had to use a different MacBook, though (still investigating this). However, my client did receive an email warning about the 32/64-bit issue that is starting Feb 1st. How do we get around that? Is Corona going to release an update to automatically solve it?

Any apps you release before Feb 1, 2015 can have 32 bit slices.  You only have to worry about this if you are releasing after 2/1 and we hope to have a solution to this before we get to that date.

Rob

Okay, thanks Rob!

BTW I have no idea why my computer can’t make good signing requests.

1.) Uninstalled Xcode

2.) Restarted

3.) Reset Keychain Access to Default

4.) Ran Keychain Access First Aid

5.) Installed Xcode from Mac App Store

6.) Restarted

7.) Revoked my Dist. and Dev. Certificates from developer.apple.com

8.) Created Signing Request in Keychain Access

9.) Generated Dist. and Dev. Certificates

10.) Generated new App ID

11.) Created new Dev. Provisioning Profile

12.) Started Xcode

13.) Added account in Xcode Preferences

14.) Refreshed to find Certificates and Profiles

15.) Removed all provisioning profiles from iPad in Xcode

16.) Added new Dev. profile to iPad

17.) Quit and Restarted Xcode

18.) Installed today’s Corona SDK Daily Build

19.) Opened app, published using Dev. profile

20.) In Xcode, tried to add app to iPad

21.) Got error  App Installation Failed. The application does not have a valid signature.

And again, on my wife’s MacBook Pro, no problems whatsoever. It’s all on mine even after reinstalling Xcode and setting Keychain to Default.

Can you build a very basic project in Xcode?

Rob