When it comes to setting up push notifications properly, while straightforward, it is important to pay attention to a few key steps.
Below are the main steps to review and assist with QA to ensure pushes are setup correctly and will be delivered to devices as expected.
Did you follow all the steps?
This is the first step and question we’ll go over in order to ensure that you have set up push notifications properly.
If you followed the documentation, and things aren’t working as expected, please revisit the docs again to make sure you’ve implemented every step.
Check out the Taplytics Apple Push Docs here.
Are Push Notifications turned on in Xcode?
While we agree that this is a silly question, more times than not, it’s a step can be easily glossed over, especially if you’re zooming through the steps.
Have you uploaded your push certificates for development and production environments?
In order for Apple to recognize your certificate and for us to route the push notifications properly, we need you to upload your dev and production environment push certificates shown here.
Your source of truth - the Apple Developer Portal
The Apple Developer Portal is going to be your friend in terms of determining what Apple expects from you for which bundle IDs and relevant app ID you should be using from Xcode.
With that said, the thing to look out for is bundleIDs and matching it to the relevant app ID and comparing it to what you have set up in Xcode
Here’s an example where if you don’t choose the right bundle identifier and match it with the relevant app ID during the sandbox and production certificate process, your set up will not work.
If your User Segmentation shows 0 users with push notifications enabled
- Is [Taplytics registerPushNotifications]; being triggered at any point while you’re navigating your app? If you don’t actually trigger this at any point, then it would make sense that you’re not receiving the push token and thus not able to target anyone in your user segmentation.
- Is the push opt-in modal being triggered? If the user can’t get the token, then they can’t receive the push
- To ensure that you’re properly receiving the push token, you should use Charles Proxy to verify if your app is pulling the push token down from Taplytics
You can revisit the docs on this here.
Are you targeting the right environment?
Verify that you’re pulling down the push token properly through Charles Proxy or through User Insights.
With Charles, you’ll be looking for
- isActive being true and isPushEnabled being true as well
- a presence of a push token
In User Insights, depending on which environment you’re targeting, you’ll be looking for YES in either Push Token or Sandbox Push Token as shown below.
Hopefully, with this debugging guide, you're able to get back on the right track and start sending out push campaigns. If you have any other questions - feel free to reach out to us on your Private Slack channel if you haven't already, message us in the chat box on the Taplytics.com website, or email us at email@example.com.