This error (pictured above) shows up on the main browser console (not the Reactime extension console) occasionally, not always.
Still not sure what causes it, or what functionality exactly is affected, if any at all.
The previous iteration team seemed to attempt solving this issue by returning true at the end of the port.onMessage and chrome.runtime.onMessage event handlers in our background.js script file.
One of these attempts is reproduced in screenshot-form, below:
Why it might be happening?
Issue #206 : an uncaught error in our extension that breaks the chrome runtime connection.
This error (pictured above) shows up on the main browser console (not the Reactime extension console) occasionally, not always. Still not sure what causes it, or what functionality exactly is affected, if any at all.
The previous iteration team seemed to attempt solving this issue by returning
true
at the end of theport.onMessage
andchrome.runtime.onMessage
event handlers in ourbackground.js
script file. One of these attempts is reproduced in screenshot-form, below:Why it might be happening? Issue #206 : an uncaught error in our extension that breaks the chrome runtime connection.