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
Our bug tracking system is reporting "Cannot read property 'sendMessage' of undefined" coming from the faye library.
This does not happen everytime or for all users or on a specific action or message.
The full stack we have so far is:
Error: Cannot read property 'sendMessage' of undefined
at c._sendEnvelope in
Upon further investigating we found that the error was either that _transport or dispatched or undefined at the moment of this error. Creating a safeguard on our end would result in this being overwritten upon deploy, when it will do a npm install to fetch the latest faye package.
Is this a known issue, and is there any resolution for this?
Kind regards,
Dave Bleeker
The text was updated successfully, but these errors were encountered:
It looks like you're referring to the Dispatcher._sendEnvelope() function. This has a guard the start to check that this._transport exists, and the call to this._transport.sendMessage() is synchronous with that guard. You'd need to find a way for this._transport to become unset between the guard passing and sendMessage() being called.
Our bug tracking system is reporting "Cannot read property 'sendMessage' of undefined" coming from the faye library.
This does not happen everytime or for all users or on a specific action or message.
The full stack we have so far is:
Error: Cannot read property 'sendMessage' of undefined
at c._sendEnvelope in
Upon further investigating we found that the error was either that _transport or dispatched or undefined at the moment of this error. Creating a safeguard on our end would result in this being overwritten upon deploy, when it will do a npm install to fetch the latest faye package.
Is this a known issue, and is there any resolution for this?
Kind regards,
Dave Bleeker
The text was updated successfully, but these errors were encountered: