简体   繁体   English

在App Store上进行iphone ad-hoc分发

[英]iphone ad-hoc distribution on app store

I made an error and put an ad-hoc distribution instead of appstore distribution to an appstore approved app. 我犯了一个错误,并将ad-hoc分发而不是appstore分发到appstore批准的应用程序。

What are the problems that I might encounter? 我可能遇到的问题是什么? Will the user who buys the app be entitled to install the app to 100 devices like the ad-hoc distribution? 购买应用程序的用户是否有权将应用程序安装到100个设备,如ad-hoc发行版? Or is it going to be fine? 还是会好起来的?

The same thing happened to me, and the app has sold hundreds of copies with no reviews indicating an incorrect profile. 同样的事情发生在我身上,该应用程序已售出数百份副本而没有任何评论显示错误的个人资料。 I imagine either Xcode or Apple fixed it for us, though I'm not certain how. 我想Xcode或Apple都会为我们修复它,虽然我不确定如何。 That said, however, I would update it the next time around. 但是,我会在下一次更新它。

我不小心使用AdHoc配置文件将App上传到AppStore,与Panagiotis一样,app已获批准并准备出售。

If you signed it with the wrong certificate, Apple will reject it and it won't be distributed to end users. 如果您使用错误的证书对其进行签名,Apple将拒绝该证书,并且不会将其分发给最终用户。

I'm surprised that it wasn't immediately rejected on upload to be honest. 我很惊讶,上传时没有立即拒绝,说实话。 But if you're sure it's the wrong version you can reject the binary yourself in iTunes Connect. 但如果您确定它是错误的版本,您可以在iTunes Connect中自行拒绝二进制文件。

Provisioning profile does the following: 供应配置文件执行以下操作:

  • ties your app id to your distribution certificate and optionally a list of devices 将您的应用ID与您的分发证书以及可选的设备列表相关联
  • also enforces that the binary matches entitlements like key-chain access group 还强制二进制文件匹配权限,如密钥链访问组

The difference between adhoc and appstore profiles for the same app: 同一个应用的adhoc和appstore配置文件之间的区别:

  • the adhoc one includes a list of devices that can install .... adhoc adhoc one包含可以安装的设备列表.... adhoc

The certificate, app id and entitlements are EXACTLY the same 证书,应用程序ID和权利完全相同

Binary: 二进制:

  • Your provisioning profile is embedded into the binary produced from Organizer archive. 您的配置文件嵌入到Organizer存档中生成的二进制文件中。 I have in the past submitted adhoc builds with no issues. 我过去提交的adhoc版本没有任何问题。 And I just done another one yesterday to put my money where my mouth is. 我昨天又做了一次,把我的钱放在嘴边。 Will let you know if it passes the review process. 如果通过审核流程,会通知您。

I'm not advocating to be lazy and just use one profile. 我不是主张懒惰而只是使用一个档案。 Organizer archive does give you the option to re-sign with a specific profile so you have no excuses. 管理器存档确实为您提供了使用特定配置文件重新签名的选项,因此您没有任何借口。 And Apple may (or already have) introduce other information in the profiles in future so not worth the risk unless you curious like me. Apple可能(或已经)在未来的配置文件中引入其他信息,除非您像我一样好奇,否则不值得冒险。

You can pretty much count on your app being rejected by Apple for not being signed with the proper certificate. 您可以非常依赖Apple拒绝使用正确的证书签署您的应用程序。

It may be worthwhile rejecting the current binary and uploading the properly signed distribution binary rather than waiting on Apple to reject. 可能值得拒绝当前二进制文件并上传正确签名的分发二进制文件而不是等待Apple拒绝。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM