Set up push notifications for TestFlight builds?

Hi,


I'm confused about what the right way is to configure TestFlight builds to get push notifications.


My app identifier is configured to support push notifications in both the development and production environments. I have both SSL certificates installed on my server. When I make a build with Xcode and install it on a device through a USB cable, the device is able to get a device token and send it to the server (and the server is later able to generate a push notification).


However, when I compiled the same app and distributed it through TestFlight, the TestFlight builds never even report a device token to the server.


In the old days I remember that we used to have to explicitly create an Ad Hoc profile for apps that used push notifications. Is this still required? This was always something of a pain and I had hoped that it wasn't needed with the new TestFlight, particularly since I do not know the device IDs of all my testers anymore.


Thanks.

I am new to push notifications and Test Flight; however, I have an App that is distributed via Testflight and a server that is running and sending out push notifications. You do not need to know the device tokens of your Testflight testers; however, the application needs to get the device token and send that to the server when it "registers".


I do not use Ad-Hoc provisioning, and as far as I have noticed, a Testflight App behaves exactly like a real production App. My server is configured to send via the production gateway and it is working -- the only issue I have is that once I put a passphrase on my cert/key PEM file, it seems to break the push...but, that is independent of the App, and not sure what is causing that.

Set up push notifications for TestFlight builds?
 
 
Q