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
Since I upgraded from esendex-notifier 6.2 to 6.3 I get an error message from esendex : "400 - No messages were supplied"
Profiler with 6.2 =>
Profiler with 6.3 =>
How to reproduce
upgrade the symfony/esendex-notifier in the composer.json to 6.3
run composer update symfony/notifier
Possible Solution
As you can see in the profiler the "messages" is missing a dimension so it's serialized as an object instead of an array of objects.
So updating this =>
To this =>
Seems to do the trick :
Additional Context
No response
The text was updated successfully, but these errors were encountered:
…froy)
This PR was squashed before being merged into the 6.3 branch.
Discussion
----------
[Notifier] Fix Esendex messages serialization
| Q | A
| ------------- | ---
| Branch? | 6.3
| Bug fix? | yes
| New feature? | no
| Deprecations? | no
| Tickets | Fix#50892
| License | MIT
It seems that the "messages" is missing a dimension since 6.3 and its serialized as an object instead of an array of objects.
Commits
-------
3826587 [Notifier] Fix Esendex messages serialization
Symfony version(s) affected
6.3
Description
Since I upgraded from esendex-notifier 6.2 to 6.3 I get an error message from esendex : "400 - No messages were supplied"
Profiler with 6.2 =>
Profiler with 6.3 =>
How to reproduce
composer update symfony/notifier
Possible Solution
As you can see in the profiler the "messages" is missing a dimension so it's serialized as an object instead of an array of objects.
So updating this =>
To this =>
Seems to do the trick :
Additional Context
No response
The text was updated successfully, but these errors were encountered: