您最近向 App Store 提交的二进制文件 -
在我通过存档提交我的应用程序后, 我在我的 iPhone 中进行测试,并在发布之前使用分发配置 我收到来自应用商店的电子邮件:
无效签名 - 确保您使用分发证书而不是临时证书或开发证书签署您的应用程序。验证 Xcode 中的代码签名设置在目标级别是否正确(覆盖项目级别的任何值)。此外,请确保您上传的包是使用 Xcode 中的 Release 目标而不是 Simulator 目标构建的。如果您确定代码签名设置正确,请在 Xcode 中选择“Clean All”,删除 Finder 中的“build”目录,然后重建您的发布目标。
更正这些问题后,请转至应用程序的版本详细信息页面(位于 iTunes Connect 的“管理您的应用程序”模块中),然后单击“准备提交二进制文件”。继续完成提交过程,直到应用程序的状态为等待上传。然后,您可以使用应用程序加载器上传更正后的二进制文件。
After I submit my app via archive ,
I test in my iphone and I use distribution configuration before i publish
I received email from app store :
Invalid Signature - Make sure you have signed your application with a distribution certificate, not an ad hoc certificate or a development certificate. Verify that the code signing settings in Xcode are correct at the target level (which override any values at the project level). Additionally, make sure the bundle you are uploading was built using a Release target in Xcode, not a Simulator target. If you are certain your code signing settings are correct, choose "Clean All" in Xcode, delete the "build" directory in the Finder, and rebuild your release target.
Once you have corrected these issues, go to the app's version details page (found in the Manage Your Applications module of iTunes Connect) and click Ready to Submit Binary. Proceed through the submission process until the app's status is Waiting for Upload. You can then use Application Loader to upload the corrected binary.
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(2)
只是进行新的构建&再次将其上传到应用程序商店,但确保在活动目标中您已使用分发证书:)
just make new build & upload it to appstore again but make sure in active target you have used distribution certificates :)
我多次收到此错误,每次都是出于相同的原因。我只是通过在目标和项目级别选择我的分发配置文件来解决它。我不知道这是否是正确的解决方案,但它每次都解决了我的问题。因此,只需尝试在所有调试、发布和分发配置中选择分发证书即可。如果您使用的是 xCode 4
,请参阅随附的屏幕截图。
希望这有帮助。
I got this error lots of time with same reason every time. I just resolved it by selecting my distribution profile in target and project level both. I don't know if it is correct solution or not but it solved my problem every time. So just try to select distribution certificate in all the debug, release and distribution configuration. See attached screenshot if you are using xCode 4
.
Hope this help.