Skip to content
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

Keep getting error message "null is not an object (evaluating 'this.connection.handlesActivityChecks')" #233

Closed
cowardcalf opened this issue May 18, 2017 · 7 comments

Comments

@cowardcalf
Copy link

cowardcalf commented May 18, 2017

Hi, our production have this error.

We've been using Pusher-js in our production for a long time.
Since about 6 months ago, we keep receiving an error like
null is not an object (evaluating 'this.connection.handlesActivityChecks').

The errors have been reported by our Raygun service, may not be able to reproduce that.

Looks like it happens for some particular users using Safari.

The users' environments is
Mac OS 10.11.6 / 10.10.5 / 10.12.3 etc.
Safari 10.0.3

The version of pusher-js is from ^3.0.0 to ^4.0.0.

This issue could be similar to #82

@cowardcalf
Copy link
Author

cowardcalf commented May 18, 2017

The error stack is like this:
image

@cowardcalf
Copy link
Author

Hi, @pl, @jpatel531, would you guys be able to help or give any advice?

@Sparkmasterflex
Copy link

I'm currently getting this issue too. Any progress on this?

screen shot 2017-10-23 at 8 51 51 am

screen shot 2017-10-23 at 8 52 15 am

@cowardcalf
Copy link
Author

@Sparkmasterflex, I've talked with them via submitting a support ticket.

They reckon that could be a racing issue but not affecting the normal use.
It's more like an unnecessary error message.
They said they would fix that in the future. 😅

@hph
Copy link
Contributor

hph commented Oct 24, 2017

Hi, are you using the latest version of the library (4.2.1)?

@Sparkmasterflex
Copy link

I am not. I believe there was a reason that we're stuck at 3.0.0

Does one of the later releases specifically correct this? I have a number of external React components that I would have to upgrade and I believe the last time I tried a minor 3.x upgrade it completely broke one.

I can try to upgrade but don't want to spend the time if it's just a "it could help"

Thanks for the replies

@hph
Copy link
Contributor

hph commented Oct 25, 2017

@Sparkmasterflex It was fixed in this commit and is included in version 4.2.0 and above (see release notes). I completely forgot to close this issue and notify subscribers about it. Sorry about that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants