Closed ilyabochkov1331801 closed 9 months ago
Hey there! We recently implemented sandbox support. We should only use the sandbox when the token is associated with a debug build. We haven't added a way to view this information in the UI but potentially if you can provide us with the token in question we can tell you which environment it is using.
0a57d226fcdeefe957dd2e430cdccb4b9c0aa62ae44f5531a5f499e512efb9bf problem with this token. We got it from TestFlight build so there is a production token
Look at this screenshots
1) error info from klaviyo (BadDeviceToken)
2) succeed sent push using same token and production environment
3) failed push using sandbox (same error)
Ahh got it ok I will check on this token.
We are looking into this on our end @ilyabochkov1331801 in the mean time here is some thing you can try if you already haven't -
Uninstall all debug and prod apps from the device and install just the test flight app and see if you are able to send a push. We released a new feature today that can be used to send a test push to a single device from the push content builder. You can bring up this modal using the "Send Preview" button at the top right.
It works now) I got notification using push preview and using compaign on the same build. I will ask QA to check and close issue if all will be fine
Description
Hello. One of the my colleagues report a problem and haven’t had any answer https://community.klaviyo.com/members/alena-n-14748. Looks like klaviyo sends pushes using sandbox endpoint because of we have same result using side service
Checklist
main
branch of this package.Expected behavior
No response
Actual behavior
No response
Steps to reproduce
No response
The Klaviyo Swift SDK version information
2.2.1
Destination operating system
iOS 16
Xcode version information
No response
Swift Compiler version information
No response