-
Notifications
You must be signed in to change notification settings - Fork 305
Report reason message get truncated #237
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
Comments
Hi. During sending the notifications we also get a lot of error messages with code 403. All solutions that we found in the Net leads us to GCM. It's not clear for us what is really happening. Should we unsubscribe the subscriber or should we retry sending notifications. Also according to the UserAgent information all subscribers with those errors use Chrome browser on Android OS. If anyone have some thoughts or infrmation about situation like this please HELP to resolve it. |
I have the same problem, any solution? |
I had the same problem but was solved after generating new vapid keys, I don't really know what I did wrong with the previous keys |
Looks like this is a long-known issue in Guzzle. I'll make a PR to fix this once my last PR is approved. |
Hey! I wonder if there's a solution for this at this point? |
NOTE: Please test in a least two browsers (i.e. Chrome and Firefox). This
helps with diagnosing problems quicker.
Setup
Problem
When I use the wrong subscription for sending web push, $report->getReason() were truncated, like this:
Expected
The error message should not truncated.
Features Used
Example / Reproduce Case
Send notification with wrong subscription data with this format:
but with wrong subscription. Program should showing error message that truncated.
Other
When I search from internet, message gets truncated because of calling
$reason->getMessage()
at WebPush class line 180. When I change it to$reason->getResponse()->getBody()->getContents()
I get complete message but without mentioning endpoint.The text was updated successfully, but these errors were encountered: