TypeError: undefined is not an object (evaluating 'this._callbacks')
See original GitHub issueUnfortunately we don’t have a ton of info on this but some of our users (looks like a couple users repeatedly across the span of the past few months) have been getting an unhandled javascript error of TypeError: undefined is not an object (evaluating 'this._callbacks')
, which appears to be coming from the pusher.js library. Is it possible this is a bug in the pusher js library?
Issue Analytics
- State:
- Created 8 years ago
- Comments:22 (10 by maintainers)
Top Results From Across the Web
TypeError: undefined is not an object (evaluating 'this.props ...
TypeError : undefined is not an object (evaluating 'this.props') when trying to use callback between child and parent in React.js.
Read more >Native callback: TypeError undefined is not an object ... - GitHub
Hi, I made this quite sometime back. Now I am unable to compile it on my end. I will try to fix it...
Read more >27/3 - TypeError: undefined is not an object (evaluating 'family ...
Here's the message: TypeError: undefined is not an object (evaluating 'family[i].name') The code outputs the right values to the console, ...
Read more >ajax call: "undefined is not an object (evaluating... - ServiceNow
Solved: I had a user complaining they are not able to use a certain page while using Safari on MacOS/Sierra which utilizes an...
Read more >undefined is not an object (evaluating 'dataText[i].length')
TypeError : undefined is not an object (evaluating 'dataText[i].length') ... 100); } // text finished, call callback if there is a callback function...
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 FreeTop 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
Top GitHub Comments
Just curious if anyone is still having this problem?
Maybe it doesn’t like the
name
variable being shadowed. Try renaming the innername
variable toname_