向 iTunesConnect 提交应用程序更新（疯狂！）

发布于 2024-08-03 21:13:24 字数 1220 浏览 6 评论 0原文

iTunes connect 不断拒绝我的应用程序更新二进制文件，这让我抓狂。通常我能弄清楚，但我已经尝试了我能想到的一切。也许有人可以帮忙:)

我得到的错误是：

您上传的二进制文件无效。签名无效，或者不是使用 Apple 提交证书签名。

我正在将应用程序的更新版本上传到商店。当前版本是1.0，新版本是3.0。这是我尝试过的：

使用以下命令压缩应用程序包命令行（我听说 Finder zip 实用程序有时可能很糟糕）
检查我的应用程序是否已正确签名与 $>; codesign -vv myApp （说 “在磁盘上有效）
在构建中检查记录正确的配置垃圾那里
在确保我的 Info.plist 文件 CFBundleVersion 和 CFhortBundleVersion 是从我当前的版本增加

这就是到目前为止我能想到的检查内容，据我所知，一切看起来都很好。

现在我在门户网站的某个地方读到，您必须使用与以前相同的分发证书来签署更新，我是（我认为）。但是，我必须使用新的配置文件进行签名，因为我用于 App Store 的旧配置文件已过期（或者其他什么，我不知道它不起作用）。

关于我的情况需要了解的事情

此更新实际上是从新模板完全重写，但我已确保使用完全相同的应用程序 ID（通配符）和捆绑包标识符），因此这不应该成为问题。

另外，自从上次提交到应用程序商店以来，我已经更换了机器，但我记得从我的旧机器中导出了所有内容（我认为）。我这里还保留着旧的，上面有所有相同的数据，如果这有帮助的话。我不认为我忘记了什么）。

提前感谢您的任何帮助:)

更新

所以我决定尝试使用应用程序加载器上传，看看它是否会给我任何新的错误，它确实出现了此进入控制台。也许有人可以在那里找到一些有意义的东西。

另外值得注意的是，门户指南表示更新必须使用用于签署原始应用程序的原始分发配置文件进行签名。我尝试过使用那个旧的，但 Xcode 不允许我选择它，因为有“没有匹配的密钥对”或其他什么。有办法解决这个问题吗？根据钥匙串，我已经得到了我的分发证书及其私钥，这一切看起来都是有效的。我已确保尝试修复钥匙串以防万一，但没有任何改变。

原文

iTunes connect keeps rejecting my binary for an application update and it's driving me mad. Usually I can figure it out but I've tried everything I can think of. Maybe someone can lend a hand :)

The error I'm getting is:

The binary you uploaded was invalid. The signature was invalid, or it was not signed with an Apple submission certificate.

I am uploading an updated version of my app to the store. The current version is 1.0, this new one is 3.0. Here's what I've tried:

Zipped the app bundle with the
command line (I've heard the Finder
zip utility can be bad sometimes)
Checked my app is signed properly
with $> codesign -vv myApp (says
"Valid on disk)
Checked in the build
log for the correct provisioning junk
to be there
Made sure in my
Info.plist file the CFBundleVersion
and CFShortBundleVersion are
incremented from my current version

That's what I can think of to check so far, and everything looks good as far as I can tell.

Now I've read somewhere in the Portal that says you must sign updates with the same Distribution Cert as before, and I am (I think). However I have to sign with a new provisioning profile because the old one I used for App Store has expired (or something, I don't know it just won't work).

Things to know about my situation

This update is actually a complete re-write from a new template, BUT I've made sure I'm using the exact same App ID (wildcard) and bundle indentifier) so that shouldn't be a problem.

Also, I've switched machines since I last submitted to the App Store but I remembered to export everything (I think) from my old machine. I still have the old one here, with all the same data on it, if that's helpful. I don't think I've forgotten anything).

Thanks in advance for any help :)

Update

So I've decided to try uploading with the Application Loader to see if it will give me any new errors, and it has, it spewed this out into the console. Perhaps someone can find something meaningful there.

Also of note, the Portal Guide says Updates must be signed with the original Distribution Provisioning profile as was used to sign the original app. I've tried using that old one, but Xcode won't let me select it, as there's "No matching key pair" or whatever. Is there a way to remedy this? According to Keychain I've got my Distribution Cert and its private key, it all looks valid. I've made sure to try Repairing the Keychain in case, but no change.

分享到QQ

分享到微博