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

The connection has not been established yet error on console just after onclose event is triggred. #28

Open
sparkwork992 opened this issue Feb 3, 2018 · 1 comment
Assignees
Labels

Comments

@sparkwork992
Copy link

I am getting the following error on close in production
min-bower-20180201_224511-57e1187.js:136 Error: InvalidStateError: The connection has not been established yet
at d.send (min-bower-20180201_224511-57e1187.js:21168)
at b._transmit (min-bower-20180201_224511-57e1187.js:21169)
at b.disconnect (min-bower-20180201_224511-57e1187.js:21170)
at Object.disconnect (min-bower-20180201_224511-57e1187.js:21177)
at websocketService.disconnect (min-app-20180201_224511-57e1187.js:28986)
at min-app-20180201_224511-57e1187.js:28856
at m.$emit (min-bower-20180201_224511-57e1187.js:164)
at onClose (min-app-20180201_224511-57e1187.js:492)
at d.sock.onclose (min-app-20180201_224511-57e1187.js:499)
at d.c.dispatchEvent (min-bower-20180201_224511-57e1187.js:21168)

@beevelop
Copy link
Owner

beevelop commented Feb 9, 2018

Can you provide the code snippet used to provoke this issue? Is this behavior reproducible?

@beevelop beevelop added the ô¿ô label Mar 7, 2018
@beevelop beevelop self-assigned this Mar 7, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants