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

For me the problem was that I had a asset with a non-ASCII character in the filename.

Answer 2

I just had this problem while working on a bindings project for Xamarin.

The library would not bind, so I made a proxy framework which invokes the framework I needed.

It was the self-made proxy framework that were getting the ITMS-90035 error message.

After a few hours of fiddeling around I discovered a mismatch between the framework in the IPA file, and the actual content of my proxy framework.

After countless cleaning/rebuilding of the project, I manged to fix the issue by deleting the Xamarin cache on the Mac.

It is located at ~/Library/Caches/Xamarin.

After I deleted the Xamarin folder, I re-built my bindings project. I were then able to upload my app to TestFlight/AppStore.

Answer 3

I had the same problem:

My project is a client which access APIs using a non-standard Auth protocol. I implemented a library for this protocol as a separated project and imported it as a subproject in the client's one. Both projects used AFNetworking as HTTP Client. Also the client and the library uses other non-shared external libs.

This schema worked well until Xcode 6.3: all review submissions were accepted in all the stages. After updating to XCode 6.3.1 my submissions to iTunes where rejected because of unsigned .o files of the AFNetworking lib. After iterating over all the answers without success, I decided to remove the subproject. I moved all the library files to the client project and removed the redundant AFNetworking files. After doing this, the app was approved at iTunes Connect :)

It worked as a temporal solution. Probably I'll need to use CocoaPods or Carthage to be able to separate the app and the lib again.

Answer 4

Check if you have the RNGridMenu.m or .h files into the "Copy Bundle Resources" into the "Build Phases" of your target