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 use integer as messageGroupId anymore #28

Closed
bruno-rodrigues opened this issue Feb 6, 2024 · 1 comment
Closed

Cannot use integer as messageGroupId anymore #28

bruno-rodrigues opened this issue Feb 6, 2024 · 1 comment

Comments

@bruno-rodrigues
Copy link

After upgrading from Laravel 8 to Laravel 9 we upgraded to your latest version but now all the places where we used an integer as messageGroupId are failing.

In QueryCompatibleInputMiddleware.php line 165:

  The provided type for `MessageGroupId` value was `integer`. The modeled type is `string`.

Should public function onMessageGroup($messageGroupId) only accept strings (or cast inputs into string)?

Thank you

@patrickcarlohickman
Copy link
Contributor

@bruno-rodrigues ,

This was due to a change in the AWS SDK. AWS added the type checking in version 3.285.0. When you upgraded your version, it must have upgraded the SDK version being used.

While I'm sure you've since resolved the issue on your end, I have just released a patch update that will prevent the error. The MessageGroupId and MessageDeduplicationId will now be passed through strval() before being sent to AWS.

Thanks,
Patrick

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants