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 #109 the Swift_Message used for email logging is lazy-loaded. This seems to interact badly with the memory queue strategy, because it clones messages.
It seems only the initial message is properly (lazily) initialized, but the clone is not, so, this might be an error in the lazy load library as well, but I figure I mention it here since this is where I first ran into this effect.
The specific error you'll get is: Fatal error: Uncaught exception 'Swift_TransportException' with message 'Cannot send message without a sender address'
The text was updated successfully, but these errors were encountered:
Since #109 the Swift_Message used for email logging is lazy-loaded. This seems to interact badly with the memory queue strategy, because it clones messages.
It seems only the initial message is properly (lazily) initialized, but the clone is not, so, this might be an error in the lazy load library as well, but I figure I mention it here since this is where I first ran into this effect.
The specific error you'll get is:
Fatal error: Uncaught exception 'Swift_TransportException' with message 'Cannot send message without a sender address'
The text was updated successfully, but these errors were encountered: