Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Invalid calling object
See original GitHub issueNPM version: 5.6.0 Node version: 9.4.0 OS: Windows Browser: IE 11
Issue:
My application started crashing on IE11, with an error of Invalid Calling Object, after speding some time debugging, I figured out that what was causing the problem was any airbreak-js version of 1.0.*
Solution: Downgrading it to 0.9.9 fixed my issue with IE11
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Internet Explorer 11 and Edge throws error Invalid calling object
Hello, I am getting the following error in Internet Explorer 11 and Edge. It works perfectly fine under Safari, Chrome, Firefox: The file ......
Read more >Invalid Calling Object error in IE - Stack Overflow
This form seems to works though: ({}).toString();. Both forms appear to work fine in chrome, am I missing something?
Read more >TypeError invalid calling object using IE 11 : r/angular - Reddit
Hi everyone, I'm getting the error "invalid calling object" when i use IE on a function that makes an Http request, I'm using...
Read more >Easy FIX Invalid Calling Object Epic Games Launcher
Here is a simple and quick fix for Invalid Calling Object Epic Games Launcher! Epic Games Launcher pops this problem up when you...
Read more >PopupControl - The "Invalid calling object" exception is thrown ...
PopupControl - The "Invalid calling object" exception is thrown in a modal popup in IE11 if Angular is used in a project.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Same problem here. Caused by line 193 in airbrake-js/src/instrumentation/historian.ts I think this is the problem:
Seems like IE does not allow to create these kind of aliases.
Yes, I believe it is automatically updated with some delay.