Troubleshooting and Testing Push Notifications with TestFlight
TestFlight beta testing allows you to distribute builds of your app to testers, collect feedback, and prepare your app for release on the App Store. TestFlight beta testing is optional; you can submit your app for review without using it. However, it’s easy to do, free, and a valuable way to improve your app before releasing it through the App Store. You can enable TestFlight beta testing for up to 100 apps at one time in your iTunes Connect account.
For a summary of this feature, see the Apple Developers TestFlight Beta Testing overview article.
The following information describes how to test push notifications on an unpublished app or on a separate device with TestFlight.
TestFlight has a feature where the IDFA changes every few minutes within builds and reports a different IDFA then what a device is actually using. This causes a disconnect with In-App Marketing because the IDFA is used as the primary ID for each device. The IDFA that displays in the My TUNE Device App is the real IDFA associated with all of your Apps except the TestFlight downloaded App. This information is further documented in our Testing the iOS Integration with TestFlight article.
If you are testing using an iOS device, you’ll need to setup your test profile using your IP Address as the device identifier.
Important Note: Do NOT use your iOS device’s IFA as TestFlight randomizes the IFA of the device during testing. This will block TUNE from recognizing your single test device.
To test that Push is set up correctly in a production environment:
- Log the Push Token in your TestFlight build, find it in the device logs, and use the In-App Marketing App Settings screen to check that you can correctly send push. This is a reliable way to confirm that TUNE has the correct Push Certificate and everything is working properly in the SDK.
- If your build is not live in the App Store, you can publish and schedule a production test campaign. The Push Notification will come through on your device. This provides a view of a particular user, although you may not be able track them correctly through test profiles due to the limitations of TestFlight.
For more detailed information on this topic, see the Apple Developers TestFlight Beta Testing instructional article.