Hi there, I’ve implemented Klaviyo integration. It’s correctly work with TestFlight/AppStore build’s. But if I’m trying to send notification to locally built app - I see “Invalid push token” inside dashboard. How can I fix this?
Solved
Push notifications on iOS not work in debug mode
+2Best answer by Brian Turcotte
Hi
Do you have notifications disabled on your testing device? That’s one reason an invalid token might occur.
Another issue could be that the app is foregrounded (i.e., open on the device) when the notification is delivered. It is best to have the app backgrounded (i.e., closed) and the phone locked when testing if notifications are delivered successfully.
Also, here’s our Help Center article on the topic, if you haven’t already seen it:
If none of the above causes apply, then we can take a deeper look at your integration. I hope this helps get you started!
- Brian
+37Hi
Do you have notifications disabled on your testing device? That’s one reason an invalid token might occur.
Another issue could be that the app is foregrounded (i.e., open on the device) when the notification is delivered. It is best to have the app backgrounded (i.e., closed) and the phone locked when testing if notifications are delivered successfully.
Also, here’s our Help Center article on the topic, if you haven’t already seen it:
If none of the above causes apply, then we can take a deeper look at your integration. I hope this helps get you started!
- Brian
+7Hi
I’m the Klaviyo product manager for mobile push notifications. I’m assuming when you’re trying to send a notification to a local build that you’re trying to use the APNs Sandbox environment. We do not currently support Sandbox tokens, but this functionality is coming very soon. Until then, you should use TestFlight builds to ensure that push notifications are working correctly through Klaviyo if you want to test before fully publishing your app.
Thanks,
Mark
+3Hi
I’m the Klaviyo product manager for mobile push notifications. I’m assuming when you’re trying to send a notification to a local build that you’re trying to use the APNs Sandbox environment. We do not currently support Sandbox tokens, but this functionality is coming very soon. Until then, you should use TestFlight builds to ensure that push notifications are working correctly through Klaviyo if you want to test before fully publishing your app.
Thanks,
Mark
Hi Mark,
Can you further detail the “very soon”-piece above? I’m working with React Native and without APNs Sandbox support it is really hard to test and debug.
Also, a question for engineering: I struggle to collect the “_k” property on iOS, so I can do a custom $opened_push event. It works great on Android, but I struggle to capture the property on iOS specifically. Without APNs sandbox it is really hard to test and debug.
+7Also for testing purposes, you may want to make use of our new feature that enables sending preview notifications. https://help.klaviyo.com/hc/en-us/articles/18011985278875
+3Also for testing purposes, you may want to make use of our new feature that enables sending preview notifications. https://help.klaviyo.com/hc/en-us/articles/18011985278875
That’s perfect. Was already using the preview since Android don’t have the same limitations around debug/production, but this makes things easier.
I’m still unable to preview push notifications in local iOS builds using version 2.2.1. It always shows the red error banner in the dashboard mentioned above. From what you all are saying here, it seems like this should be working?
+3I’m still unable to preview push notifications in local iOS builds using version 2.2.1. It always shows the red error banner in the dashboard mentioned above. From what you all are saying here, it seems like this should be working?
I can confirm that it is working, assuming the push token gets registered correctly in Klaviyo (I register the token using API calls, not using Klaviyo’s iOS and Android packages).
Log in to the Community
Use your Klaviyo credentials
Log in with Klaviyo
Use your Klaviyo credentials
Log in with KlaviyoEnter your E-mail address. We'll send you an e-mail with instructions to reset your password.