iphone ad-hoc distribution on app store

Question

I made an error and put an ad-hoc distribution instead of appstore distribution to an appstore approved app.

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? Or is it going to be fine?

Answer 1

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. That said, however, I would update it the next time around.

Answer 2

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

Answer 3

If you signed it with the wrong certificate, Apple will reject it and it won't be distributed to end users.

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.

Answer 4

Provisioning profile does the following:

• ties your app id to your distribution certificate and optionally a list of devices
• also enforces that the binary matches entitlements like key-chain access group

The difference between adhoc and appstore profiles for the same app:

• the adhoc one includes a list of devices that can install .... adhoc

The certificate, app id and entitlements are EXACTLY the same

Binary:

• Your provisioning profile is embedded into the binary produced from Organizer archive. I have in the past submitted adhoc builds with no issues. 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.

Answer 5

You can pretty much count on your app being rejected by Apple for not being signed with the proper certificate.

It may be worthwhile rejecting the current binary and uploading the properly signed distribution binary rather than waiting on Apple to reject.