-
Notifications
You must be signed in to change notification settings - Fork 303
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
Websocket error on M1 iMac Monterey #4746
Comments
Thanks for filing! Will be useful if anyone else runs into it. Sounds like Websockets are broken on the MacOS beta @amancevice have you tried using a different browser? Wondering if they're broken on Safari, or if macOS Monterey beta has some kind of new security firewall that accidentally broke websockets. Might also be good to poke around in the macOS issue tracker |
@nicks thanks & sorry for the delay — I was out of town for a while but am back in front of my M1 iMac — I just upgraded to the latest macOS public beta and can confirm that:
I'll poke around and see what I can find |
@nicks Looks like something changed when handling websockets in Safari 15. Edit: works fine on Safari 15 / BigSur 11.6 (Intel) |
JS console reports:
It doesn’t work on the iPad (all browsers using port forward to access localhost:10350) |
Also seeing this:
Safari 15.0 macOS 12.0 |
i can repro after upgrading to Monterey! though not sure what's going on yet 🤔 |
Looks like a bug in Safari's new NSURLSession Websocket feature, which got turned on by default in Monterey. You can go to |
Here's some interesting discussion on this: Not super familiar with websocket messaging, but looks like they now declare they support |
Works on the iPad too 😬 |
Expected Behavior
tilt up [space]
should open the Tilt GUICurrent Behavior
UI is a blank page with the text
Loading...
Inspecting the console there is an error connecting to the websocket:
Steps to Reproduce
tilt up [space]
Context
tilt doctor
OutputAbout Your Use Case
Not an urgent issue as Tilt works fine on my work machine, just raising as a potential issue for future users
The text was updated successfully, but these errors were encountered: