You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am currently experiencing an issue with Gorush feedback URL configuration. Despite successfully receiving push notifications and responses in the console log, no response is being sent to the specified feedback_hook_url.
# Request body
curl --location 'http://localhost:8088/api/push' \
--data '{
"notifications": [
{
"tokens": [
"Token1"
],
"platform": 2,
"message": "This is my msg"
}
]
}'
Problem:
Expected behavior: The response should be sent to the configured feedback_hook_url. Actual behavior: No response is being sent to the feedback_hook_url. However, the response is being logged in the console.
Additional Information:
The core is running in release mode.
SSL is disabled.
Feedback headers are properly configured with a token.
The text was updated successfully, but these errors were encountered:
Hello everyone, in my case I have experienced that, during sending a couple of thousand Push Notifications, I could not get some feedback errors to the feedback url. It is minimal. Generally the case results in {1;2;3} lost feedbacks of {15000;30000}
Throughout the sendings, I use the same token and expecting it returns with a generic error.
This, using the same token with bulk sending, may also be causing to the such kind of a case.
Is there anyone experienced such kind of a case or with recommendations?
I am currently experiencing an issue with Gorush feedback URL configuration. Despite successfully receiving push notifications and responses in the console log, no response is being sent to the specified feedback_hook_url.
Core Configuration:
Problem:
Expected behavior: The response should be sent to the configured feedback_hook_url.
Actual behavior: No response is being sent to the feedback_hook_url. However, the response is being logged in the console.
Additional Information:
The text was updated successfully, but these errors were encountered: