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
It appears that the _providerState !== ProviderStates.READY .. any idea why this might be? Im not getting any errors from raygun despite having set debugMode: true perhaps this is because I set debugMode: true AFTER the init error?!
The text was updated successfully, but these errors were encountered:
After more node_modules/raygun4js/dist/raygun.umd.js spelunking I managed to track it down and get it working.
It appears that there is an order of operations issue happening where onLoadHandler is looking for apiKey to be set but it hasnt by that point so rg.init never gets called.
Hi im trying to setup raygun in my chrome extension.
It works from a website fine but for some reason not in the extension.
Im using the npm version of raygun4js.
At first I thought it was somehow filtering it out thanks to this line:
raygun4js/src/raygun.js
Line 1140 in 3c07dc1
But when I added some debug console lines around it I found out that its not event getting to that part and is instead exiting the function here:
raygun4js/src/raygun.js
Line 706 in dd4bf98
It appears that the
_providerState !== ProviderStates.READY
.. any idea why this might be? Im not getting any errors from raygun despite having setdebugMode: true
perhaps this is because I setdebugMode: true
AFTER the init error?!The text was updated successfully, but these errors were encountered: