[英]APN & TestFlight : Xcode chooses a wrong (XC*) provisioning profile to submit archive
I am using Parse.com to send client push notifications, from one iDevice to another. 我正在使用Parse.com将客户端推送通知从一个iDevice发送到另一个。
It works well with the 'development' setup, ie with - the Push Notification Setting of the appID set on 'Development' 它适用于“开发”设置,即-在“开发”上设置的appID的推送通知设置
- a development SSL certificate - a development provisioning profile With this setup, I managed to send a push notification to myself (sender = receiver = my device). -开发SSL证书-开发设置配置文件通过此设置,我设法向自己发送了推送通知(发送者=接收者=我的设备)。
Now I want to test the communication between 2 different devices. 现在,我想测试2个不同设备之间的通信。 To do so, I use TestFlight (because this is the way I usually send updates to my client).
为此,我使用TestFlight(因为这通常是我向客户端发送更新的方式)。 I followed all the recommended steps to move from Development to Ad Hoc :
我按照所有建议的步骤从“开发”转到“临时”:
The issue : the build is successfully submitted, but as soon as it is, Apple sends me this e-mail : 问题:构建已成功提交,但Apple尽快将以下电子邮件发送给我:
And, naturally, I can no longer receive/send push notifications. 而且,自然地,我无法再接收/发送推送通知。 Here's what I tried so far :
这是我到目前为止尝试过的:
Any help would be much appreciated! 任何帮助将非常感激! I have been struggling for days, it is really frustrating when the problem does not come from the code !
我已经努力了好几天,当问题不是源于代码时,这真令人沮丧! Thanks
谢谢
Thanks Rhythmic Fistman for the help. 感谢节奏拳手的帮助。 I found the answer today : I was submitting my build to TestFlight with an Ad-Hoc provisioning profile, instead of an AppStore Distribution Provisioning Profile.
今天我找到了答案:我提交我的生成与特设供应轮廓TestFlight,而不是AppStore的发行配置文件。 I had read somewhere that Xcode was creating a Ad-Hoc provisioning profile behind the scenes while submitting to TestFlight, so I thought that the Ad-Hoc profile was appropriate.
我曾读到某处Xcode在提交给TestFlight的同时在后台创建了Ad-Hoc配置文件,所以我认为Ad-Hoc配置文件是适当的。 But since TestFlight runs like the AppStore, not having registered the subscribed devices UDID in advance (as with Ad-Hoc distribution) it makes sense to use a "broader" profile such as an AppStore Distribution Provisioning Profile.
但是由于TestFlight像AppStore一样运行,并且没有预先注册订阅的设备UDID(与Ad-Hoc分发一样),因此使用“更广泛的”配置文件(如AppStore分发配置文件)是有意义的。
So for anyone using Push Notifications with Testflight, you do need an AppStore Distribution Provisioning Profile. 因此,对于将推式通知与Testflight一起使用的任何人,您都需要一个AppStore发行设置配置文件。 Then Xcode will automatically picks it for the submission phase.
然后Xcode将自动为提交阶段选择它。
Expunging wildcard provisioning profiles from Xcode and the developer portal can be done, but you can probably fix your problems by explicitly setting your Release Provisioning Profile to the correct Ad Hoc profile in your build settings: 可以从Xcode和开发人员门户中删除通配符配置文件,但是您可以通过在构建设置中将您的Release Provisioning Profile显式设置为正确的Ad Hoc配置文件来解决问题:
This should stop Xcode getting too creative when Archiving. 这样可以避免Xcode在存档时变得太有创意。
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.