Yeah it happens predictably but not deterministically with our Phoenix app. I can often enter a state of infinite reload within 30s of clicking around. But sometimes it happens right on first page load, and I don’t have any other open tabs to the same app.
jakemauer
dblack
Yeah, sounds similar, but you’re seeing it a lot more frequent than I was experiencing. Are you seeing it in both prod and dev? You’ve ruled out other browsers? You’re not seeing any errors in the server during the loop?
It’s pretty frustrating, because I couldn’t consistently trigger it. All I did find is that in dev, disabling the Endpoint code_reloader in dev.exs seemed to stop the cycle. Also, in prod, it came out of the cycle for no apparent reason after about 60-90 minutes. But that could all be coincidence.
0
dblack
jakemauer
So I’ve now tried wrapping the new LiveSocket... and liveSocket.connent() code in window.addEventListener(“DOMContentLoaded”) and no dice. I still get websocket errors and reloads.
0
wanton7
I think it’s this issue WebSocket sometimes fails to reconnect until browser restart or website access from incognito mode · Issue #15410 · brave/brave-browser · GitHub
Linked issue Hasura WebSocket closed before connection is established error while trying to create subscription · Issue #4509 · hasura/graphql-engine · GitHub sounds very similar to this problem.
1
megalithic
Just chiming in; I’ve been experiencing this in latest Brave stable and on LiveView 0.17.7. I have not tried wrapping on the DOMContentLoaded EventListener yet..
0
wanton7
I would avoid using that browser until its fixed. Because WebSockets are used quite a bit in many pages. If you are making a WebSocket using website I would detect Brave browser and give people warning about this issue until they fix it.
0
hellosmithy
Is anyone aware if this is still an issue with Brave in general?
I’ve been running Phoenix on localhost in Brave (with shields down) and it seems to fall back to long polling after the first websocket response. I’m not sure if this is just a localhost issue or not, but it works fine in Chrome.
0
dblack
I’m no longer using Brave, but I only had the issue happen a couple of times, then never again.
Your sticking to longpoll issue sounds like something I’ve experienced (with chrome). I posted about it here LiveView falls back to longpoll after dev server restart
Basically, websocket is used in dev environment until I kill the dev server and restart. After that any existing browser tabs connected to the server will use longpoll, but new browser sessions use websocket.
1
hellosmithy
Basically, websocket is used in dev environment until I kill the dev server and restart. After that any existing browser tabs connected to the server will use longpoll, but new browser sessions use websocket.
Ah this was it - thanks!
1