-
Notifications
You must be signed in to change notification settings - Fork 37
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
Better Error Handler #25
Comments
Hi @vinkla, this error should have been fixed with #13. Its strange to encounter this problem again, in the response you provided the JSON response, what is the HTTP response code associated to the request ? Is it a 4XX or 5XX response code ? If it is I think your problem is related to issue #24. We'll improve error management in version |
I can't really remember the response and it is now quite hard to test since my account now is paid. I also think that could be related to #24 |
Ok, I think the problem you describe is fixed in version So I suppose you were using version I'll publish version |
Aah, that is probably why. Good that we found it then. |
Have you setup auto publishing for this repo on Packagist? Or do you do it manually? |
Yes, I think the problem was that the version was not equal to the GIT tag in the We've just published a new |
Today our premium account had ended and we had no idea what was going on until I tried making a request directly against the Pushwoosh API. The answer from the Pushwoosh API was:
Though, this is what I got back from this library:
Maybe we can return the error messages whenever the Pushwoosh API return 210?
The text was updated successfully, but these errors were encountered: