-
Notifications
You must be signed in to change notification settings - Fork 307
Call to undefined method GuzzleHttp\Exception\ConnectException::getResponse() in WebPush.php line 185 #300
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
Getting this issue too.
|
I had the same issue but when I added the following code, the error went away and the logs say successful but I didn't see a notification (which might be a seperate issue)
|
Related #299 |
I have the same issue. I am using the latest version v6.0.3. |
same problem here |
Same problem here, looks like it's affecting v6.0.3 |
In my case it's related to the number of notifications I process in a flush operation (I don't change the default limit to 1.000). If I send 800 that error occurred, however with 200 it's fine. Could this be related to a transitional error caused by out of memory or a network error as in #203 ? |
The error is indirectly caused by guzzle. They decided to no longer inherit ConnectException from RequestException, thus the getResponse method is not available anymore. You can see it in the following commit: There is a pull request above with a fix but a syntax test failed without further details as it seems. However the fix itself is trivial. Either downgrade guzzle to 6.5.5 or check for response availability. Affected are all versions of this lib from v6.0.0 upwards Quick fix for your project until the fix is ready: |
Hi @tbyte80, the idea you propose is good, this clears the error, but the notifications are not delivered to the devices, my project was working fine, then I started with the error and now I have no errors, but the notifications are not delivered. Any suggestion? |
Is there any working solution yet? I am having exactly same issue. |
There might be another issue, in This prevents my messages to be sent. |
@Minishlink, are you still interested in maintaining your code? |
Adressed in #299, root cause is #300 (comment) |
Besides taking 6 months to approve the pull request, I think everything went very well! |
NOTE: Please test in a least two browsers (i.e. Chrome and Firefox). This
helps with diagnosing problems quicker.
Setup
Problem
Exception
Expected
No exception
Features Used
Example / Reproduce Case
Other
It never happened before v6.0.2 but it could be because HTTP request never failed.
Also as I can see - RequestException was expected but ConnectException received.
The text was updated successfully, but these errors were encountered: