Skip to content
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

Cannot send messages since esendex-notifier v6.3 #50892

Closed
raphael-geffroy opened this issue Jul 5, 2023 · 0 comments · Fixed by #50893
Closed

Cannot send messages since esendex-notifier v6.3 #50892

raphael-geffroy opened this issue Jul 5, 2023 · 0 comments · Fixed by #50893

Comments

@raphael-geffroy
Copy link
Contributor

raphael-geffroy commented Jul 5, 2023

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"
Untitled(4)

Profiler with 6.2 =>
Untitled(1)

Profiler with 6.3 =>
Untitled(3)

How to reproduce

  • upgrade the symfony/esendex-notifier in the composer.json to 6.3
  • run composer update symfony/notifier

Untitled
Untitled(2)

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 =>
Untitled(5)
To this =>
Untitled(6)
Seems to do the trick :
Untitled(7)

Additional Context

No response

@fabpot fabpot closed this as completed Jul 9, 2023
fabpot added a commit that referenced this issue Jul 9, 2023
…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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants