-
Notifications
You must be signed in to change notification settings - Fork 75
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
content-available: 1 is not attached to a transactional message #113
Comments
I'll also add, this affects our ability to set badge count remotely. This does not work, I would expect this to relay directly to the device
|
here's something interesting. I started to work directly with the REST API and found out this payload works, but link (for deep linking) no longer works.
The moment I remove |
update: figured out that link needs to be in |
I'm working with an Expo mobile project, in which I'm trying to listen to background notifications.
I managed to get it working through the customer.io transactional dashboard, using this custom payload:
When I try with the ruby gem using
custom_payload
on the request body, I get none of the background listeners to execute, but I get the push notification. I suspect"content-available": 1
is not getting carried over to the transactional message payloadAny pointers would be greatly appreciated!
The text was updated successfully, but these errors were encountered: