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
All of a sudden we started receiving these errors from your API method.
We haven't changed anything that I'm aware of that might cause this issue, but I'm ready to investigate.
Could not denormalize object of type "object", no supporting normalizer found.
File: /var/www/vendor/symfony/serializer/Serializer.php
Line: 211
We are using ViberImageMessage as an object that we are passing to sendViberImageMessage method of Infobip\Api\ViberApi;
The code was intact for more than several weeks, but this error started occurring last Thursday. It may be that there is something wrong underneath with dependencies, since the error comes from the Seralizer, but I have no clue what is going on, and how to dig deeper and debug your library.
Any help would be appreciated since we rely a lot on these Viber messages. Thanks for the understanding.
UPDATE
Ok, I actually managed to dig deeper into this library and debug and find out where the error comes from.
Error is happening at Infobip\ObjectSerializer on line 119 (method deserialize).
What happes is that GuzzleHttp returns a HTTP error 500, and then your code throws new ApiException, which gets caught and calls sendViberImageMessageApiException, which further tries to deserialize the HTTP response, but fails at telling the ObjectSerializer the correct class name, which ends at symfony/serializer who knows nothing about the class name "object"
So, this is the actual error I get from your API (yes, I will contact the support):
{"requestError":{"serviceException":{"messageId":"GENERAL_ERROR","text":"Something went wrong. Please contact support."}}}
But this is the problem in this library that causes the original error I reported:
It should be of type stdClass instead of object.
If I'm not mistaking anything, I can make a PR for this.
Cheers!
The text was updated successfully, but these errors were encountered:
All of a sudden we started receiving these errors from your API method.
We haven't changed anything that I'm aware of that might cause this issue, but I'm ready to investigate.
We are using ViberImageMessage as an object that we are passing to sendViberImageMessage method of Infobip\Api\ViberApi;
Here's how it looks:
The code was intact for more than several weeks, but this error started occurring last Thursday. It may be that there is something wrong underneath with dependencies, since the error comes from the Seralizer, but I have no clue what is going on, and how to dig deeper and debug your library.
Any help would be appreciated since we rely a lot on these Viber messages. Thanks for the understanding.
UPDATE
Ok, I actually managed to dig deeper into this library and debug and find out where the error comes from.
Error is happening at Infobip\ObjectSerializer on line 119 (method deserialize).
What happes is that GuzzleHttp returns a HTTP error 500, and then your code throws new ApiException, which gets caught and calls sendViberImageMessageApiException, which further tries to deserialize the HTTP response, but fails at telling the ObjectSerializer the correct
class name
, which ends at symfony/serializer who knows nothing about the class name "object"So, this is the actual error I get from your API (yes, I will contact the support):
But this is the problem in this library that causes the original error I reported:
It should be of type
stdClass
instead ofobject
.If I'm not mistaking anything, I can make a PR for this.
Cheers!
The text was updated successfully, but these errors were encountered: