Hi all, I'm on the phone with a client and were both a little confused. He managed to get self hosted push working by setting all of codesigning in xcode as development. He then archived, and selected adhoc, and then xcode showed a option for his certificate and he just chose his distribution. It then worked. So I checked my app, switched it all to development in xcode, and then archived it. xcode asked me which app name/version on itunes to choose, and then the profile it should use, I chose distribution, and it submitted as a update fine. So the question is: why give us a option to choose what certificate to use during the archive/distribution process if you have to choose them in xcode settings as well? Why not only once? Wondering, would this fix push notifications? Will keep you all updated once the app I submitted with development settings under a distribution signed submission gets approved and tested with self hosted push. Cheers, David https://buzztouchmods.com

I could be wrong, but I recently did some ad hoc work and this is what I gathered from it (not 100% related to your push question, but worth noting). When I build an archive with a distribution profile, I use the organizer to submit the app to the store, and all goes well. When I ask xcode to build an .IPA, it asks me what profile I want to use regardless of how I signed the archive. So, I believe its asking me to "re-sign" the binary, or giving me an opportunity to do so, without having to change my xcode setting and re-build. With this in mind, I'm guessing the thought-precess behind it is: I could archive an app (distribution) as normal, but then I might want to have some people test the app before submitting it. So I would log into app dev and setup a few adhoc certificates, and then I could just re-sign the archive as an .IPA without changing what I already compiled. Hope that makes sense.