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

Done.

Thank you for contacting Apple Developer Technical Support (DTS). This acknowledgment is automatically generated and does not require a reply.

I know it’s related to this machine only because Charles McKeever was kind enough to screen share with me over the weekend and when he and I repeated the same steps in the same order, it worked for him and not for me.

Then I did it again on my wife’s computer and it worked for me. Then I threw this laptop out of a 2nd story window in frustration, but it still didn’t help. :wacko:

Apple responded to my tech support ticket with the obligatory how-to guide of creating provisioning profiles. I responded with step-by-step screenshots of every possible step from creating certificates to trying to get an Xcode-created Hello World app to appear on my device instead of just the iOS Simulator.

After going back and forth with Apple and proving to them it’s not something I’m doing, they admitted they have no clue what’s wrong. They said I should just open a bug report, which I’ll have to do later. Maybe it’s the same for you, Charlie?

Yes, exactly the same for me over here and has been for the past few months. I’ve got 2 projects finished for clients and can’t publish because of this issue. I have been through the Apple support queue several times and have not gotten anyone that knows why this is happening.

A bug report MAY get results but I’m skeptical. Worth a try though. Please let me know if they are able to figure it out.

In the meantime, I’ll try what Rob suggests and see if I can get a simple “Hello World” app submitted and take it from there.

Yeah, I’ll keep you posted. The guy who has been offering tech support is going to follow up with the bug reporting engineer who gets the report as well. Here’s what I tried and listed in my report:

Mid 2012 MacBook Pro

OSX 10.10.1
Xcode 6.1.1 (also later tried 6.2 beta 4)
Application Loader 3.0
Keychain Access 9.0

Creating certificate signing request, certificates, App ID, and provisioning profiles on one MacBook Pro leads to “App Installation Failed. The application does not have a valid signature.” when trying to test the app on iPad 3.

Replicating same steps in same order on a different MacBook Pro results in correct build and ability to test on same iPad 3. Both MacBooks have the same specs and software.

Steps to Reproduce:
Steps to Attempt Correction:
1.) Uninstall Xcode 6.1.1 and Restart MacBook Pro
2.) Re-install Xcode 6.1.1
3.) Restart MacBook Pro
4.) Reset Keychain Access 9.0 to Default
5.) Run Keychain Access First-Aid
6.) Revoke All Certificates from developer.apple.com
7.) Delete App IDs from developer.apple.com
8.) Delete Provisioning Profiles from developer.apple.com
9.) Remove Provisioning Profiles from iPad 3 via Xcode 6.1.1
10.) Delete App Developer Account from Xcode > Preferences
11.) Create new Certificate Signing Request in Keychain Access 9.0
12.) Create new Development and Distribution Certificates on developer.apple.com using Certificate Signing Request
13.) Create new App ID called “MyApp” on developer.apple.com
14.) Create Development and Distribution Provisioning Profiles using MyApp
15.) Download Certificates and Provisioning Profiles
16.) Add Developer Account via Xcode Preferences
17.) Refresh Account to display Development/Distribution Certificates & Provision Profiles
18.) Add Development Provision Profile to iPad via Xcode > Devices
19.) Restart Xcode
20.) Open HelloWorld app.
21.) Set up Xcode to Automatically Manage Profiles as recommended by Apple Developer Technical Support (https://developer.apple.com/library/ios/qa/qa1814/_index.html#//apple_ref/doc/uid/DTS40014030)
22.) Attempt to test on iPad and receive “App installation failed. No code signature found error.”
23.) Uninstall Xcode 6.1.1
24.) Restart Computer
25.) Install Xcode 6.2 Beta 4
26.) Repeat steps 3-22

I finally am able to test apps on my iPhone and iPad! An update is now available for OSX Yosemite (10.10.2) so I installed that and now I can test apps on my devices again.

Explains why I never had any issues prior to updating to Yosemite.

Glad that’s solved!