-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
null is not an object (evaluating 'this._transport.transportName') #448
Closed
kichik opened this issue
Aug 6, 2018
· 1 comment
· May be fixed by dyna-dot/create-react-app#9, anyulled/rhte-demo#3 or saurabharch/create-react-app#3
Closed
null is not an object (evaluating 'this._transport.transportName') #448
kichik opened this issue
Aug 6, 2018
· 1 comment
· May be fixed by dyna-dot/create-react-app#9, anyulled/rhte-demo#3 or saurabharch/create-react-app#3
Comments
A simple workaround for now is to replace it with: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Using Sentry to report user exceptions, I get a lot of the following error:
I believe it's coming from:
sockjs-client/lib/main.js
Line 311 in 0ab53b8
I have a separate issue where I'm unable to use the minified version due to #393. Since I'm using the non-minified version, the
debug()
calls are still there in the code and cause this issue.It looks like some kind of a race condition where the connection is closed before
_open()
is called. It's only the next line that checks for that case. Thedebug()
call assumes the connection is open and accesses_transport
like it's open.I'm not sure what the best solution for this would be, but in my case I just commented out that line and it seems to resolve the issue.
The text was updated successfully, but these errors were encountered: