iPhone:应用程序安装因“无效签名者”而失败错误

发布于 2024-08-23 12:18:41 字数 469 浏览 5 评论 0原文

iPhone 连接到运行最新 iTunes 版本的 Mac,我 100% 确定她的 UDID 在配置文件中。她的iPhone还没有越狱,我们甚至还恢复了出厂设置。

我在这一台 iPhone 上安装我们的开发版本时遇到问题。错误是:

应用程序“[应用程序名称]”不是 安装在 iPhone“iPhone”上 因为签名者无效

我 100% 确定 UDID 已准确输入到配置文件中,并且他们正确复制了正确的配置文件/构建组合。该组合已成功安装在十几部 iPhone 上。

我们已经能够在某些设备上安装它,没有任何问题。

编辑:

从评论到答案:

我们可以将它安装在 100 部 iPhone 上 我们的帐户。我们有大约 40 部 iPhone 在此配置文件中 适用于其中 38 个。

The iPhone is attached to a Mac runnning the latest iTunes version and I am 100% sure that her UDID is in the provisioning file. Her iPhone has not been jailbroken and we even restored it to factory settings.

I am having trouble installing our development build on this one iPhone. The error is:

the application "[Application Name]" was not
installed on the iPhone "iPhone"
because the signer is not valid

I am 100% sure that the UDID is accurately entered in the provisioning file and that they correctly copied the right provision file/build combo. This same combo has been successfully installed on over a dozen iphones.

We have been able to install this on some devices with no problems.

Edit:

From comments to an answer:

We can install it on 100 iphone with
our account. We have about 40 iphones
in this provisioning profile and it
works on 38 of them.

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(8

萌逼全场 2024-08-30 12:18:41

我有一个似乎对遇到麻烦的用户有效的修复:

  1. 删除所有有问题的配置文件并
  2. 重新启动
  3. 应用程序添加回配置文件第一
  4. 同步设备
  5. 现在再次添加应用程序资源
  6. 同步以在设备上获取应用程序

有问题的机器是 Windows 盒子。不知道这是否有影响。

如果其他人遇到此问题 - 尝试此操作并让我们知道这是否是实际的修复或解决方法!这种妖精很少见,而且是用同样的步骤解决的。

这是我的修复想法的参考:

http://iphone.forums .wordpress.org/topic/installing-beta#post-1194

I had a fix that seemed to work for one user who was having troubles:

  1. remove all offending profiles and apps
  2. restart
  3. add back provisioning profile FIRST
  4. sync device
  5. now add app resource
  6. sync again to get app on device

the offending machine was a windows box... dunno if that makes a difference.

If someone else gets this issue - try this and let us know if this is the actual fix or workaround! This goblin has rarely been seen and solved with the same steps.

this was my reference for the fix idea:

http://iphone.forums.wordpress.org/topic/installing-beta#post-1194

零時差 2024-08-30 12:18:41

我们可以使用我们的帐户将其安装在 100 部 iPhone 上。此配置文件中有大约 40 部 iPhone,它适用于其中 38 部。还有其他想法吗?

我会告诉巴兹你打个招呼,如果你能帮助我们,我们会给你一块月球岩石!

We can install it on 100 iphone with our account. We have about 40 iphones in this provisioning profile and it works on 38 of them. Any other ideas?

I'll tell Buzz that you say hi and if you can help us we'll get you a moon rock!

垂暮老矣 2024-08-30 12:18:41

(忽略:我误读了问题,没有注意到他已经安装了几十个,所以我的建议不适用)

如果您只有标准开发者帐户,则在证书进一步失效之前,您最多只能安装在五部手机上安装。如果您已经在五部手机上安装了它,那么这很可能就是问题所在。

告诉 Buzz,互联网上有一个随机的人说:“嗨!”

(Ignore: I misread the question and didn't notice he had dozens of installs already so my advice does not apply)

If you have just the standard developers account, you can only install on up to five phones before the certificate becomes invalid for further installs. If you've already installed it on five phones that is most likely the problem.

Tell Buzz some random guy on the internet said, "Hi!"

高速公鹿 2024-08-30 12:18:41

可以尝试以下几件事:

  1. 在开发人员门户上更新配置文件。它可能已过期或已损坏。
  2. 创建新的配置文件

A couple of things to try:

  1. Renew the profile at the Developer's portal. It may have expired or become corrupt.
  2. Create a new provisioning profile
看轻我的陪伴 2024-08-30 12:18:41

这个问题的答案对您有帮助吗?

签名者无效错误

将签名置于目标级别,而不是项目级别

我个人不确定这意味着什么,但在这种情况下它有效

Does the answer to this question help you at all?

Signer not valid error

Put the signing at the Target level, not the Project level

I'm personally not sure what that means but it worked in that case

野却迷人 2024-08-30 12:18:41

同步后 mobileprovision 文件是否显示在设备上?您应该在中看到它,

Settings->General->Profiles

如果没有,那就是问题所在。再次检查 UDID 是否正确 - iTunes 和开发者门户中的 UDID 相同。尝试将 iTunes 与 mobileprovision 同步,而不尝试安装该应用程序。如果仍未安装,请检查 UDID。如果它安装在所有其他设备上,则 UDID 很可能是问题所在。

Does the mobileprovision file show up on the device after sync? You should see it in

Settings->General->Profiles

If it doesn't then that would be the problem. Check once again that the UDID is correct - same UDID on iTunes and in the developer portal. Try syncing iTunes with the mobileprovision without trying to install the app. If it still doesn't get installed then CHECK THE UDID. If it is getting installed on all other devices, UDID is most likely the issue.

耶耶耶 2024-08-30 12:18:41

如果分发签名证书同时被撤销并重新创建,您需要首先从设备中删除旧的配置文件。这是在 iOS 3.1.3 设备上。

If the distribution signing certificate was revoked in the meantime and recreated, you need to remove the old provisioning profile from the device first. This is on an iOS 3.1.3 device.

最单纯的乌龟 2024-08-30 12:18:41

这件事最近发生在我身上,我解决了。情况是,我有一个临时配置文件,已成功用于大约 40 台带有多个不同应用程序的设备。当需要新设备时,我会将其添加到配置文件中,下载,然后使用 XCode 中的“共享”与相同的存档应用程序但新的配置文件。

最近,我的分发证书过期了,因此我创建了一个新的分发证书并重新创建了配置文件。随后,我仍然可以在现有设备上安装,但尝试在新设备上安装时会出现错误,即使我已将它们添加到配置文件中并在设备上安装了配置文件。

秘密是,虽然我已经创建了新的分发证书并将其添加到我的钥匙串中,但钥匙串中仍然有旧证书的副本,并且它被用来签署应用程序。事实证明,如果您不从 XCode 中删除旧的配置文件,当您启动 XCode 时,它​​将在 KeyChain 中重新创建旧的证书,并将用于对应用程序进行签名,这意味着新的配置文件将使用新的配置文件设备(使用新证书创建)将不匹配。

解决方案:续订证书时,删除使用该证书签名的所有旧配置文件,删除旧证书,然后重新创建、下载并安装新配置文件。

This happened to me recently and I resolved it. Situation was that I had an ad hoc provisioning profile I was using successfully for around 40 devices with several different apps. When a new device was required I would add it to the profile, download, then use 'share' from XCode with the same archived app but the new profile.

Recently my distribution certificate expired, so I created a new one and recreated the provisioning profiles. Subsequently, I could still install on the existing devices but would get an error trying to install on new devices, even though I had added them to the profile and installed the profile on the device.

The secret was that although I had created the new distribution cert and added it to my KeyChain, there was still a copy of the old cert in the KeyChain, and that was being used to sign the app. It turns out that if you do not delete the old provisioning profiles from XCode, when you start up XCode it will recreate the old cert in the KeyChain, and that will be used to sign the app, which means that the new profile with the new device (created with the new cert) will not match.

Solution: when you renew your cert, delete all the old profiles signed with that cert, delete the old cert, then recreate, download and install the new profiles.

hth

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文