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
I'm experiencing a similar issue. In my case I'm serializing messages to offload the delivery via a command line background task. The message can't be serialised. This is because the backing store adds subscriptions when objects are set on the message, such as ItemBody and FileAttachments. The subscriptions are closures and can't be serialised.
Here's test version of how I used to serialize my messages:
$message = new Message();
$message->setSubject('Test');
$body = new ItemBody();
$body->setContentType(new BodyType(BodyType::HTML));
$body->setContent('<p>Test</p>');
$message->setBody($body); // Causes a subscription to be set on ItemBody
$test = serialize($message); // This would be stored for the background task.
This bombs at the last line because the wrapped SDK Message cannot be serialised as the ItemBody backing store has a subscription attached for the message which is a closure and can't be serialised.
When I get a model from the graph, I get the correct model. But I'm using caching in Symfony to save requests.
In my local machine, this gives no trouble, when testing this.
On my remote machine, I get an error
It seems the serialization does not work well on this model?
Any suggestions?
Tim
The text was updated successfully, but these errors were encountered: