This is a question that has been bugging me for a while. I started my app (now submitted -- not yet approved) not wishing to get into the mess that is APNS (Push).
这是一个困扰了我一段时间的问题。我启动了我的应用程序(现在已经提交——还没有批准)，不想陷入APNS (Push)的混乱。
I did the following:
我做了以下几点:
iPhone Developer Center: Provisioning Portal->Provisioning: Then I created a Development and a Distribution Provisioning Profile. I installed both in XCode. Everything hunky dory. The Development profile scares me a bit by expiring so soon (90 days) but I can remove it from the iPhone(s) and sign it with a new one later. I tested using the Development profile, and later to submitted it by signing it with the Distribution profile. I then uploaded the Distribution profile-signed app to iTunesConnect (app store).
iPhone开发人员中心:供应门户——>供应:然后我创建了一个开发和分配供应配置文件。我在XCode中安装了这两个。一切都好算了。很快(90天)就要到期了，这让我有点害怕，但我可以把它从iPhone上删除，然后再签一个新的。我测试了使用开发概要文件，然后通过与分布概要文件签署它来提交它。然后，我将发布文件签名的应用程序上传到iTunesConnect (app store)。
Okay, I understand that much. Now, what I don't understand is this: Now that I understand the theories and methods behind how Push works, I am wishing to add it to my app.
好吧，我很理解。现在，我不明白的是:既然我理解了Push背后的理论和方法，我想把它添加到我的应用中。
I already went under: iPhone Developer Center: Provisioning Portal->App IDs: and created a Development Provisioning Profile and Distribution Provisioning Profile there (push & in-app purchase enabled).
我已经进入了:iPhone开发者中心:供应门户->应用程序id:并在那里创建了一个开发配置配置文件和分发配置文件(push & in-app purchase)。
Here is where it gets confusing to me. All the books and docs I have read say that I have to sign the app with this "App ID" provisioning profile (push-enabled) from now on.
这就是让我感到困惑的地方。我读过的所有书籍和文档都说，从现在开始，我必须用这个“应用ID”配置文件(支持推)来签署这个应用程序。
Does that mean I no longer ever use the previously created provisioning profiles?
这是否意味着我不再使用以前创建的配置文件?
If I were to import these "App ID" provisioning profiles into Xcode they will exist alongside my previously generated "non-push" profiles. ~/Library/Mobile Devices/Provisioning Profiles now has 2 files. One Devel and one Distrib. It will now have 4 even though for this app I will not use the "non-push" anymore right? (actually, since they are locked by using bundle-codes and app ids i will never use it again if all of my further versions of this app use Push?)
如果我将这些“应用ID”配置文件导入Xcode，它们将与我以前生成的“非推送”配置文件一起存在。~/库/移动设备/配置文件现在有两个文件。一场宴会，一场宴会。它现在有4个虽然这个应用我不会再使用"非推送"对吧?(实际上，由于它们是通过绑定码和应用id锁定的，如果我的其他版本都使用Push的话，我就不会再使用它了。)
Confused.
困惑。
Can anyone enlighten me? Why not use the "App ID" profiles in the first place for everyone -- even if you are not gonna use push? Would keep it simpler. Should I only generate "Push Enabled" profiles from now on -- even if i am not sure I am gonna use push (or for that matter in-app purchase)?
谁能开导我?为什么不在每个人的第一个地方使用“应用ID”配置文件——即使你不打算使用push?将保持它的简单。从现在开始，我是否应该只生成“Push Enabled”配置文件——即使我不确定我是否要使用Push(或者在应用内购买)?
Please give me some insight. I do not wanna do this wrong.
请给我一些建议。我不想做错。
Thanks!
谢谢!
Jann
Jann
2 个解决方案
#1
2
Based on what you stated,
根据你所说的，
All the books and docs I have read say that I have to sign the app with this "App ID" provisioning profile (push-enabled) from now on.
我读过的所有书籍和文档都说，从现在开始，我必须用这个“应用ID”配置文件(支持推)来签署这个应用程序。
it seems that your original certificates will not be valid. I am not sure why Apple does this, but they make it quite clear that provisions using Push are NOT the same as those that do not.
看来您的原始证书将无效。我不确定苹果为什么要这么做，但他们明确表示，使用Push的条款与不使用Push的条款不同。
My assumption is based on this: A provisioning profile that has a "wildcard" bundle ID cannot use APNS. They are very strict about what is what.
我的假设是:具有“通配符”绑定ID的配置文件不能使用APNS。他们对什么是什么非常严格。
I am not sure of the reason either, but I would assume it has to do with security and other factors.
我也不确定原因，但我认为这与安全性和其他因素有关。
#2
0
I think there would be some edit options besides downloading options for provisioning files. not sure much on this..
我认为除了下载配置文件之外，还有一些编辑选项。对此我不太确定。
#1
2
Based on what you stated,
根据你所说的，
All the books and docs I have read say that I have to sign the app with this "App ID" provisioning profile (push-enabled) from now on.
我读过的所有书籍和文档都说，从现在开始，我必须用这个“应用ID”配置文件(支持推)来签署这个应用程序。
it seems that your original certificates will not be valid. I am not sure why Apple does this, but they make it quite clear that provisions using Push are NOT the same as those that do not.
看来您的原始证书将无效。我不确定苹果为什么要这么做，但他们明确表示，使用Push的条款与不使用Push的条款不同。
My assumption is based on this: A provisioning profile that has a "wildcard" bundle ID cannot use APNS. They are very strict about what is what.
我的假设是:具有“通配符”绑定ID的配置文件不能使用APNS。他们对什么是什么非常严格。
I am not sure of the reason either, but I would assume it has to do with security and other factors.
我也不确定原因，但我认为这与安全性和其他因素有关。
#2
0
I think there would be some edit options besides downloading options for provisioning files. not sure much on this..
我认为除了下载配置文件之外，还有一些编辑选项。对此我不太确定。