New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Uncaught TypeError: Cannot set property 'impl' of null #344
Comments
This is odd, let me see if I can figure out what might cause this, I've never heard of it before. |
For reference, this was while using the v2.0.4 snippet |
Tried this again just now with v2.1.3 and ran into the same problem. Here's a copy of the reversed stack trace (so bottom up) I'm seeing, line by line, since it's been minified together with our code:
|
I am a little confused, are you including the snippet in a javascript file with other code and then minifying the whole thing? That doesn't seem to really make a lot of sense with how the snippet is designed. You should probably just be importing the package and using a bundling system to handle the loading then. |
I have this issue as well: I am receiving this error in the console with the rollbar script on our site. It's a Magento site. The error points column 5438 of line 234(the line of the rollbar script). Support told me to leave a message here. Our site is https://www.theorganicbloom.com. Let me know if I can be of any assistance |
Same here. Possible relation with Prototype 1.7 library. The stack trace says it calls that library but didn't had time to review it more deeply. Had to revert to Rollbar.js 1.8 |
Is there any update to this issue? |
This will be worked on for the next release, which should be within the next few weeks. Sorry for the delay! |
@rivkahstandig3636 Can you please share whether this has been released yet? We are eagerly waiting on a fix as this issue renders our error tracking useless! Thank you. |
@mlent It unfortunately got pushed back, but should be coming out with a release next Monday. I'm sorry about that! |
I'm not sure if it's related, but I keep getting |
@rivkahstandig3636 Thanks for the update - it would be really helpful to know as soon as this is available, as our other errors are totally drowned out by this one. Thanks! |
Status update? |
HUZZAH! Thank you @functionalStoic for giving me a live demo with the bug. It took me a while to track this down, but this is happening because Prototype is monkey patching WTF??? Suppose we do
In a normal world you would observe this:
If you include prototypejs:
The best fix is to stop using Prototypejs, that kind of global behaviour is troubling. However, I understand that might not be possible for a variety of reasons, let me see what I can do about a fix that works with Prototype now that I know what is going on. |
Also if anyone is seeing this error and they are not including Prototype that would be good to know because that would mean there is something else going on. But I strongly suspect this is the culprit. |
@rokob thanks for getting to the bottom of this! can you please share how soon you expect this to be released? thanks! |
I'm merging a bunch of stuff right now and will do a release later today. |
Thank you very much! |
@rokob I am still receiving the same error after having updated to the new 2.4.2. Any ideas. I changed the script tag to refer to the 2.4.2. Does the whole script need to change? Maybe something I did incorrectly? You can check www.theorganicbloom.com to see the error in the console. I completely agree with not using PrototypeJS. That kind of global behavior is troubling indeed. Unfortunately, it is still built into Magento and extracting it would be quite challenging if not impossible. Do I need to open a new issue about it as this one has been closed? |
The entire snippet needs to change. For some updates the snippet does not change so you are safe just changing the version inside the string inside the snippet, but there is not guarantee that is true with any given update. In this particular case the conflict with Prototype had to do with something going on in the snippet code so this will keep happening specifically until the entire snippet is replaced. Here is the version associated with v2.4.2
|
@rokob I have replaced the snippet. I'm now receiving a fair amount of other errors in the console regarding the rollbar line of code. You can see them by going to https://www.theorganicbloom.com. Not really sure what to do about them |
I'm closing this issue since the original issue is fixed. @functionalStoic if you're still running into problems, could you open a new issue w/ the details? |
I'm not sure what the exact repro conditions for this error is, as it didn't seem to be breaking consistently everywhere our code was used. We had previously been using an older version of the JS Rollbar snippet:
which was throwing the error referenced in #98. And while we weren't double-loading Rollbar (in so far as rollbar.min.js was only ever requested once), as far as I could make out from the latest minified snippet on https://rollbar.com/docs/notifier/rollbar.js/, there now seem to be some NPE guards, so we tried updating to the latest, only to get reports of the error mentioned in the title.
The text was updated successfully, but these errors were encountered: