Error itms-90035 - Xcode

Question

I developed a phonegap application that works great on an iPhone. Now I want to send the application to the Appstore. The following is the procedure I'm following to submit my application:

• Open Xcode and archive the project
• Click on confirmation (which is successful)
• Click "Submit" in the appstore (where I get the following error)

Until last night I didn’t even get this error, and this morning I am archiving the project and I am getting this error. I don’t know what the problem is.

This is the final step, which prevents me from submitting the application and is very frustrating, I tried to find the same error code in the stackoverflow forum, and I could not find a single message that is exactly the same error code as mine, which is very strange.

Please, help:)

Answer 1

I had the same problem, it turned out that one of my libraries installed through bower included a .sh file that was not needed. I just deleted the file and everything was downloaded successfully.

It seems that Apple is now forcing developers to have .sh files in their applications. Since the Cordova / Phonegap application does not need any of them, you can safely remove them.

Answer 2

This happened to me after upgrading to the latest Xcode (6.3.1). These are not just .sh files, as I was getting these errors in node scripts. It seems that ANY file starting with #! / Usr / bin / env will lead to these errors. I was able to cause arbitrary errors by adding #! to a random file.

Temporarily removing the #! / Usr / bin / env directive from the top of the files will work, but you need a better long-term solution :)

You will need to fix this by referring to each script file in each case, which makes sense in your project.

As noted above, this may be a temporary issue on the part of Apple, not necessarily related to the version of Xcode.

Answer 3

EDIT: I was able to avoid this error by deleting my projects .sh files from my target .

So far, I would say that the error is on the side of Apple.

Yesterday I sent the application without any problems, rejected it today to send a slightly modified binary today, but like you, I am facing the same error now. I thought this was due to Xcode6.3.1 because I installed it this morning, so I installed Xcode 6.3.0 , but the error remained. Then I carefully check everything:

• Certifications
• Provisioning Profiles
• iTunes connect application status

But so far no success.

The fact that a Google search for “itms-90035” returns only 1 result makes me think it could be a temporary incident.

Answer 4

As others said, the problem is related to the inclusion of files with the name "upload-dsym.sh" in the application package. Here are the steps that I took to overcome this error: I went to the project settings in Xcode and selected the "Target" application icon. Selected the tab "Construction Phases". Clicked on "Copy Bundle Resources" Looked at the file that was copied with the name "upload-dsym.sh". I deleted this file and then the download went fine.

Answer 5

This has something to do with the included .sh files , not the obvious one.

---

In our case, it was the AudioKit library. README says:

In most cases, when creating for iOS or tvOS, regardless of how you install the framework, you need to add a launch phase to the target of the project with the following script:

"$BUILT_PRODUCTS_DIR/$FRAMEWORKS_FOLDER_PATH/AudioKit.framework/fix-framework.sh"

---

Sometimes you do not see them directly in your target build phases . Some of the third-party libraries may cause this error, as they deal with .sh files .

See the third-party / pods README library files for more details.

Answer 6

I have the same problem. Then I delete the .sh file. And I will send my application again. Successful!

Answer 7

This issue was resolved in CrittercismSDK CocoaPods 5.2.0: https://github.com/CocoaPods/Specs/blob/master/Specs/CrittercismSDK/5.2.0/CrittercismSDK.podspec.json

You can either go to sdk 5.2.0, or delete the file and remove the following lines from the Pods-resources.sh file:

  if [[ "$CONFIGURATION" == "Debug" ]]; then install_resource "CrittercismSDK/CrittercismSDK/dsym_upload.sh" fi if [[ "$CONFIGURATION" == "Release" ]]; then install_resource "CrittercismSDK/CrittercismSDK/dsym_upload.sh" fi 

thank

Answer 8

Today we had a very similar problem and it was resolved.

ERROR ITMS-90035: "Invalid Signature" Sealed resource is missing or invalid. The binary on the path [MyNiftyApp.app/MyNiftyApp] contains an invalid signature. [...] "

We use Jenkins-CI for the build process along with the xcode plugin. When I looked at the jenkins build log, I found this error message:

 file added: /Users/Shared/Jenkins/Home/workspace/RELEASE_STAGE_my-nifty-app/build/MyNiftyApp.app/MyNiftyApp.app file modified: /Users/Shared/Jenkins/Home/workspace/RELEASE_STAGE_my-nifty-app/build/MyNiftyApp.app/Assets.car ] Codesign check fails : /Users/Shared/Jenkins/Home/workspace/RELEASE_STAGE_my-nifty-app/build/MyNiftyApp.app: a sealed resource is missing or invalid 

After searching for this Assets.car, I found this post: https://issues.jenkins-ci.org/browse/JENKINS-21253 The user had a similar problem, he could solve it by deactivating the next option of the plugin "Xcode → General assembly settings → Generate archive? "(This was true before that, now it's a lie).

At least that solved the problem on our side - perhaps it will lead you in the right direction.

Answer 9

I solved this by simply deleting the “binary” file in the error.

For you, your www / js / release.sh.

For me, these were two redundant bower files, a .sh file and a .js file, which was located under the bin folder (perhaps that is why he thought it was a binary file?).

On a side note, it seems that you can still continue the download process by simply clicking Submit after the errors in the Application Loader are presented.

Answer 10

I got the same error when I tried to download the application using ApplicationLoader 3.0. Updating to ApplicationLoader 3.1 (i.e. the latter) fixed the problem for me.

Answer 11

The directory directory is running:

 grep -r '#!/usr/' * 

This will show you all the files that can be executed. This usually includes .sh and node files.

From the search results are the files that are in the project folder (for example, the folder of my project - platform / ios / www / *), and delete them, leaving the rest.

Answer 12

there is another folder in your directory with the same file, just delete it and try creating and loading again.

Answer 13

For me there is a do-git file in the library used. I deleted it and it will work! Guys, make sure that you clearly see all the files in the Copy bundle resources in the Build Phases tab, and I'm sure you will find a solution

Answer 14

I had the same problem using both xcode 6.3.1 and 6.4 beta. My said this is my main.o file. I looked into the package resources, and for some reason there was my main project file. I deleted it and archived again to send to itunes connect for testflight and it booted normally. Took me 3 hours to realize that it was a dumb file. It helps. It seems you need to really pay attention to what you send in this section "Copying Bundle Resources" in the build phases. No matter what file it tells you, you need to remove taht from this area and try.

Answer 15

There is a related issue when .py files also confuse Xcode:

https://omz-forums.appspot.com/pythonista/post/5857432475533312

Answer 16

In my case, I got an error while sending the re-signed ipa file. It turned out that I looked at the application package in Finder, and he created the .DS_Store file (this was after re-signing using codesign , which would complain if the file was present at the time of signing).

After deleting the .DS_Store file, the download was successful.

Answer 17

I had exactly the same problem. I wrote a bug in myApp.app/myApp Decision: look for files that start with special characters or characters other than English. I found, deleted and it worked!