错误 itms-90035 - Xcode

Error itms-90035 - Xcode

提问by Nikhil Rao

I have developed a phonegap application which is running absolutely fine on iPhone. Now, I want to submit the app to the appstore. Following is the procedure I am following to submit my app:

我开发了一个 phonegap 应用程序，它在 iPhone 上运行得非常好。现在，我想将应用程序提交到应用程序商店。以下是我提交我的应用程序所遵循的程序：

1. Open Xcode and archive the project
2. Click on validate (which is successful)
3. Click on Submit to appstore (which is where I am getting the following error)

1. 打开Xcode并归档项目
2. 点击验证（成功）
3. 单击提交到应用商店（这是我收到以下错误的地方）

Until yesterday night, I wasn't even getting this error and today morning, I archive the project and I get this error. Not sure what the issue is.

直到昨天晚上，我什至都没有收到这个错误，今天早上，我归档了项目，却收到了这个错误。不确定是什么问题。

This is the final stage which is stopping me from submitting the app and is very frustrating, I tried to search for the same error code on the stackoverflow forum and I could not find one single post which is exactly of the same error code as mine, which is very strange.

这是阻止我提交应用程序的最后阶段，非常令人沮丧，我试图在 stackoverflow 论坛上搜索相同的错误代码，但我找不到一个与我的错误代码完全相同的帖子，这很奇怪。

Please help :)

请帮忙 ：）

采纳答案by Kate Miháliková

I had the same problem, turns out that one of my libraries installed via bower includes a .shfile, which is not needed. I have just deleted the file and everything has been uploaded successfully.

我遇到了同样的问题，结果是我通过 bower 安装的一个库包含一个.sh不需要的文件。我刚刚删除了文件，一切都已成功上传。

Seems like that Apple now enforces developers to have .shfiles in their apps signed. As Cordova/Phonegap app don't need any of them, you can safely delete them.

似乎 Apple 现在强制开发人员对.sh他们的应用程序中的文件进行签名。由于 Cordova/Phonegap 应用程序不需要它们中的任何一个，您可以安全地删除它们。

回答by cayleyh

This happened to me after updating to the latest Xcode (6.3.1). It's not just .sh files, as I was getting these errors about node scripts. It appears that ANY file that starts with #!/usr/bin/env will cause these errors. I was able to cause arbitrary errors by adding a #! to a random file.

这发生在我更新到最新的 Xcode (6.3.1) 后。这不仅仅是 .sh 文件，因为我收到了有关节点脚本的这些错误。似乎任何以 #!/usr/bin/env 开头的文件都会导致这些错误。我可以通过添加 #! 到一个随机文件。

Temporarily deleting the #!/usr/bin/env directive from the top of the files will work but you'll want a better long-term solution :)

暂时删除文件顶部的 #!/usr/bin/env 指令会起作用，但您需要一个更好的长期解决方案:)

You'll have to fix it by dealing with each script file case-by-case for what makes sense in your project.

您必须通过逐个处理每个脚本文件来解决它，以便在您的项目中有意义。

As noted above this could be a temporary problem on Apple's side, not necessarily related to Xcode version.

如上所述，这可能是 Apple 方面的临时问题，不一定与 Xcode 版本有关。

回答by Ferschae Naej

EDIT: I managed to avoid this error by removing my projects .sh files from my target.

编辑：我设法通过从目标中删除我的项目 .sh 文件来避免此错误。

So far I'd say that's a bug on Apple's side.

到目前为止，我会说这是苹果方面的一个错误。

I submitted an app yesterday without any issue, rejected it today to submit a slightly altered binary today, but like you I'm now encountering the same error. I thought it was related to Xcode6.3.1because I installed it this morning so I installed Xcode 6.3.0again but the error remained. Then I checking everything thoroughly:

我昨天提交了一个没有任何问题的应用程序，今天拒绝了它，今天提交了一个稍微改变的二进制文件，但和你一样，我现在遇到了同样的错误。我认为这与Xcode6.3.1因为我今天早上安装它有关，所以我Xcode 6.3.0再次安装，但错误仍然存​​在。然后我彻底检查了一切：

• Certificates
• Provisioning Profiles
• iTunes connect application status

• 证书
• 配置文件
• iTunes 连接应用程序状态

But no success so far.

但至今没有成功。

The fact a "itms-90035" Google search returns only 1 result makes me think that may be some temporary incident.

“itms-90035”Google 搜索仅返回 1 个结果的事实让我认为这可能是一些临时事件。

回答by DCG

As others have said, the problem appears to be due to including files named "upload-dsym.sh" in the app bundle. Here are the steps I took to get past this error: Went to the project settings in Xcode and selected the "Target" app icon. Selected the Build Phases tab. Clicked on "Copy Bundle Resources" Looked for a file being copied named "upload-dsym.sh". I removed that file and then the upload went fine.

正如其他人所说，问题似乎是由于在应用程序包中包含名为“upload-dsym.sh”的文件。以下是我为克服此错误而采取的步骤：转到 Xcode 中的项目设置并选择“目标”应用程序图标。选择了构建阶段选项卡。单击“复制捆绑资源”查找名为“upload-dsym.sh”的正在复制的文件。我删除了该文件，然后上传正常。

回答by Jakub Truhlá?

It has something to do with included .sh files, not that obvious indeed.

它与包含有关.sh files，确实不是那么明显。

---

---

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

在我们的例子中，它是 AudioKit 库。README 说：

In most cases, when building for iOS or tvOS, regardless of how you install the framework, you will need to add a run phase to your project's target with the following script:

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

在大多数情况下，在为 iOS 或 tvOS 构建时，无论您如何安装框架，您都需要使用以下脚本向项目的目标添加运行阶段：

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

---

---

Sometimes you don't see them directly in your target's build phases. Some of the 3rd party librariescan cause this error because they are dealing with .sh filesas well.

有时您不会直接在目标的build phases. 某些3rd 方库可能会导致此错误，因为它们也在处理.sh files。

Check your 3rd party libraries/podsREADME's files for more info.

检查您的3rd party libraries/podsREADME文件以获取更多信息。

回答by MppleHero

I have the same issue. Then I delete the .sh file. And I submit my app again. Successful!

我有同样的问题。然后我删除 .sh 文件。我再次提交我的应用程序。成功的！

回答by JennieOhyoung

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

此问题已在 CrittercismSDK CocoaPods 5.2.0 中解决：https: //github.com/CocoaPods/Specs/blob/master/Specs/CrittercismSDK/5.2.0/CrittercismSDK.podspec.json

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

您可以升级到 sdk 5.2.0 或删除该文件并从 Pods-resources.sh 文件中删除以下几行：

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

Thanks

谢谢

回答by seafoxx

We had a very similar problem today and solved it.

我们今天遇到了一个非常相似的问题并解决了它。

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

错误 ITMS-90035：“无效签名。密封资源丢失或无效。路径 [MyNiftyApp.app/MyNiftyApp] 中的二进制文件包含无效签名。[...]”

We are using Jenkins-CI for the build process together with the xcode-plugin. When I reviewed the jenkins build log I found this error message:

我们将 Jenkins-CI 与 xcode-plugin 一起用于构建过程。当我查看 jenkins 构建日志时，我发现了以下错误消息：

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 that Assets.car I found this post: https://issues.jenkins-ci.org/browse/JENKINS-21253The User had a similar problem, could solve it by deactivatingthe following plugin option "XCode -> General Build Settings -> Generate Archive?" (it was true before, now it's false).

搜索该 Assets.car 后，我找到了这篇文章：https://issues.jenkins-ci.org/browse/JENKINS-21253 用户遇到了类似的问题，可以通过停用以下插件选项“XCode -> General”来解决它构建设置 ->生成存档？”（以前是真的，现在是假的）。

At least this solved the problem on our side - maybe it will guide you to the correct direction.

至少这解决了我们这边的问题——也许它会引导你走向正确的方向。

回答by J?rgen Svendsen

I resolved this by simply removing the "binary" file(s) in the error.

我通过简单地删除错误中的“二进制”文件来解决这个问题。

For you its www/js/release.sh.

给你它的 www/js/release.sh。

For me it was two redundant bower-files, a .sh-file and a .js-file that was located under a "bin"-folder (maybe thats why it thought it was a binary?).

对我来说，它是两个冗余的 bower 文件，一个 .sh 文件和一个位于“bin”文件夹下的 .js 文件（也许这就是为什么它认为它是一个二进制文件？）。

On a side-note, it seems that you could still continue the upload process by just clicking Send after being presented with the errors in Application Loader.

附带说明一下，在 Application Loader 中出现错误后，您似乎仍然可以通过单击发送来继续上传过程。

回答by steve hannah

I received this same error when I tried to upload my app using ApplicationLoader 3.0. Upgrading to ApplicationLoader 3.1 (i.e. the latest), fixed the issue for me.

当我尝试使用 ApplicationLoader 3.0 上传我的应用程序时，我收到了同样的错误。升级到 ApplicationLoader 3.1（即最新的），为我解决了这个问题。