Error itms-90035

Question

App passes validation

On upload getting error Error itms-90035

\"Invalid Signature. Code object is not signed at all. The bi

Answer 1

I tried out pretty much every solution on SO when debugging this for an app I am submitting, and realized you can get this error in many ways. Here's a summary of what is usually wrong and how to fix it.

1) You didn't select a Provisioning Profile for Distribution with a valid certificate for your PROJECT and TARGETS. Make sure you've selected a valid provisioning profile in your Build Settings for the "Release" option, and verify at developer.apple.com that your Provisioning Profile is still valid. (here: https://developer.apple.com/account/ios/profile/profileList.action)

2) Your Code Signing Identity in Build Settings is a valid one for Distribution. Make sure you've selected one that is valid and it is selected for the "Release" option.

3) Your scheme (can be found via Product -> Scheme -> Edit Scheme) for your execution type needs to be "Release" for your Build Configuration. If you are archiving your app for App Store submission, make sure you have "Release" set for the Archive build type in this window.

4) You have multiple distribution certificates in your keychain access. Try deleting the duplicate certificates from your keychain and then try to submit again.

5) One of the most evil ones.... you have a line of code that begins with "#!" at the top of one of your files, usually a ".sh" or ".py". Recently, Apple seems to be requiring these files to be code signed. Feels like a bug on their side, but for your submission just remove this line! This can happen too if you have ".sh" files besides the build script in your Pod directory.

6) You have duplicate CODE_SIGN_IDENTITY lines in your project.pbxproj file. They might look like this...

"CODE_SIGN_IDENTITY[sdk=iphoneos*]" = "iPhone Developer"; CODE_SIGN_IDENTITY = "iPhone Distribution";

Delete one of these lines and your file should be able to build correctly again.

7) Refresh the certificates and provisioning profiles in Xcode from your developer account. Xcode -> Preferences ... select your account -> View Details -> Hit the refresh button.

8) The kitchen sink approach: create a new project and load your settings from scratch. Recreate your certificates and provisioning profiles. Never fun, but this has worked for me in a few hopeless situations.

Good luck!

Answer 2

I have tried all the solution which described on Stackoverflow. I have also tried also all possibilities as said by thebhanman in first answer but didn't solved problem.

Solution worked for me :- [Upload with Application Loader]

Don't make .ipa with doing extra process like with Terminal or Itunes etc. make .ipa with xcode in export option and it worked for me.

Step 1 :- Go to Product Archive App in xcode

Step 2 :- select export option

Step 3 :- Select 1st option //-> Save for iosappstore deployment

Step 4 :- Xcode will make .ipa file of your application with date and time folder.

Note :- First Validate your app. If validation successfully done then try this with Application Loader.

I hope this will helpful for some one in future. because i waste 2 days to solve this problem.

Answer 3

I had the same problem, it was related to asset with a non-ASCII character in the filename as in other answer.

I used this command to find the files that were causing the problem:

LC_ALL=C find . -name '*[! -~]*'

I found it in another answer in this post.

Hope this helps someone.

Answer 4

Tried & tested solution:

1. Copy both RNGrid.m & RNGrid.h to another location
2. Remove both your RNGrid.m & RNGrid.h and move to trash
3. Clean and build
4. Add both RNGrid.m & RNGrid.h files back to the project and Copy it to the destination folder
5. Clean and build

This solution works for me which is also answered here: Why does one .o file in my project has no Provisioning Profile?

Answer 5

I had this problem in a Unity app that I was resigning from a Developer version to an App Store version. I resigned the app before I resigned the frameworks in the app, thus invalidating the signature of the main app file.

This was easily solved (but not easily found) by resigning the frameworks before the app itself.

Shell script example for resigning an unzipped .ipa file:

/usr/bin/codesign -f -s "<CERTIFICATE NAME>" Payload/myApp.app/Frameworks/* 
/usr/bin/codesign -f -s "<CERTIFICATE NAME>" --entitlements entitlements.plist Payload/myApp.app

Answer 6

It seems XCode starting with Version 10.0 (10A255) does not properly sign apps with PRODUCT_NAME containing umlauts like ü (and maybe other non-ASCII chars - but we haven't tested this). This is on macOS 10.13.6 (17G65) with APFS, which might be the reason as well.

It did work with the same macOS version with APFS with an earlier XCode version just fine, so we suspect it's XCode though.

Anyway, the fix is to set PRODUCT_NAME to a string without umlauts...