iPhone:生产证书的推送通知测试
我有一个简单的问题。我一直在测试我的 iPhone 应用程序的开发推送通知证书,并且运行良好。我只是想知道在向 AppStore 提交申请之前是否可以测试生产证书?我确实尝试过,但当我使用生产证书时没有出现消息。使用生产证书时,Apple 是否要求应用程序必须在 AppStore 中?
谢谢。
I have a quick question. I have been testing Development Push Notification Certificate for my iPhone App and its been working fine. I just want to know that is it possible to test Production Certificate before submitting my application to AppStore? I did try but message is not coming along when I use production certificate. Does Apple required application to be in AppStore when I use production certificate?
Thanks.
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(3)
如果您创建临时配置文件,您会发现它使用生产证书,这可能是测试它的最简单方法。
更新:
请参阅Apple 文档< /a>
这有很多步骤,但本质上是;
1) 团队负责人需要创建一个新的 DISTRIBUTION 配置文件。这是通过在创建新配置文件时选择“Ad Hoc”而不是“App Store”来完成的。顺便请注意,您不能为此使用通配符应用程序 ID,您需要为该应用程序提供一个特定的应用程序 ID,尽管您可能已经拥有该应用程序 ID。
2) 设置您的系统,以便存档构建使用新创建的临时配置,设置所需的步骤在网上有详细记录,这是一个示例。
3) 现在,当您将 .ipa 分发到链接到 Ad Hoc 配置文件的设备时,您会发现推送通知系统正在使用生产服务器。
顺便说一句,我发现 testflightapp 对于管理 Ad Hoc 构建的分发非常有用,尽管我最近才发现它,但它目前为我节省了时间,因为我正在运行 beta 测试程序。
If you create an Ad-Hoc Profile, you'll find that it uses the production certificate, that's possibly the easiest way of testing it out.
UPDATE:
See the Apple documentation here
There are a number of steps to this but in essence;
1) The team leader needs to create a new DISTRIBUTION provisioning profile. This is done by selecting "Ad Hoc" rather than "App Store" when creating a new profile. Note by the way that you can't use a wildcard app id for this, you need to have a specific app id for the application although you may well have this already.
2) Setup your system so that build for archive uses a newly created Ad Hoc configuration, the steps required for setting this up are well documented online, here is one example.
3) Now when you distribute the .ipa to devices linked to your Ad Hoc provisioning profile, you will find that the push notification system is using the production servers.
As an aside, I find that testflightapp is really useful for managing the distribution of Ad Hoc builds and although I've only discovered it recently, it's saving me hours at the moment as I'm in the middle of running a beta test programme.
对于 Adhoc 分发,请按照以下说明操作:
如何在测试设备上加载 adHoc 发行版:
要使推送通知在临时分发上工作:
在测试开发环境的推送通知时,应牢记一些严格的清单。其中大部分已经在上面提到过。但这是解决我问题的一件事,我想分享。我希望它能帮助某人。那就是:
请注意设备令牌 ID,它对于开发者来说是不同的。生产环境。
For Adhoc distribution, Please follow the instructions below:
How to load the adHoc distribution on the test device:
For Push Notifications to work on Adhoc distribution:
There are severeral checklist that one should keep in mind while testing pushnotification for development environment. Most of them are already mentioned above. But this is one thing THAT SOLVED MY PROBLEM and i would like to share. I hope it helps someone. And that is:
Please be aware of the device token-ID, which is different for the development && Production environment .
如果您想节省更多时间,可以
在生产环境中
debug1测试这些通知,而无需构建和构建通知。每次分发时,请按照以下步骤操作:如何创建新方案
单击左上角的应用程序名称:
选择“新方案...”并为其命名,
在“构建配置”下选择“发布”:
选择它,使其出现在左上角,就完成了!
1 :您不能使用发行版或临时配置来调试,请参阅此线程
Alternative
If you will to save even more time, and
debug1 test these notifications in a production environment, without having to build & distribute each time, follow these steps :How to create a new scheme
Click on your app's name, on the left corner :
Select "New scheme..." and give it a name,
Select "Release" under "Build configuration" :
Select it, so it appear on the upper left corner, and you're done!
1 : you can't use the distribution nor the ad-hoc provisioning to debug, see this thread