Serialization of 'Closure' is not allowed/ Async Symfony Messenger Processor / ContextStamp about api-platform

[lhapaipai]

it seems that it works if you use Symfony serialiser

# config/packages/messenger
framework:
    messenger:
        serializer:
            symfony_serializer:
                format: json

        transports:
            async:
                dsn: '%env(MESSENGER_TRANSPORT_DSN)%'
                serializer: messenger.transport.symfony_serializer

[devnix]

I've had this problem, take a look at symfony/symfony-docs#17636 (comment)

[MariusJam]

Hi,

I'm having the same problem here. It happens when your framework.yaml contains the following:

framework:
    # Enables session support. Note that the session will ONLY be started if you read or write from it.
    # Remove or comment this section to explicitly disable session support.
    session:
        handler_id: null
        cookie_secure: auto
        cookie_samesite: lax
        storage_factory_id: session.storage.factory.native

If you comment these lines (and correctly configure your api-platform routes as stateless), the issue is fixed.

However, this is not possible every time as you might need this specific configuration in framework.yaml if your app also have some routes that are not stateless.

I've discussed a bit the point on Symfony's support channel on Slack and the original problem is that Symfony does not guarantee that the Request object is serializable. So passing it into an envelope seems problematic in itself. I guess a fix should be made Api-Platform side to ensure the envelope's content is serializable. Removing the Request from the $context before passing it to the envelope seems to be the good way to achieve but this might be a breaking change...

[lhapaipai]

Removing the Request from the $context before passing it to the envelope seems to be the good way to achieve but this might be a breaking change...

I totally agree...