-
Notifications
You must be signed in to change notification settings - Fork 92
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
Can't instantiate a connection from Safari / macos #107
Comments
thanks for reporting this. this affects safari on ios too, and you're right it's been broken for a while. my guess is safari 15 introduced something that breaks this. (also: sorry for taking a while to reply. i saw this post but other life things took priority over my cycles!) |
Good to know! I was trying to use it for a couple of weeks now and got sad that it didn't work anymore. |
So I tested this with my iPhone 7 on iOS 15.6.1. I ran three tests: Desktop created worm to iOS, iOS created worm to Desktop (file sent from Desktop), and iOS created worm to Desktop (file sent from iOS). If I create the worm from Desktop (Windows 10), iOS will never make a connection. Result 1: FAILED If I create the worm from iOS, connection is successful. When sending file from Desktop, file is sent to iPhone. Result 2: PASSED If I create the worm from iOS, connection is successful. When sending file from iOS, file is sent to Desktop. Result 3: PASSED Hope this helps someone? |
it turns out a safari websocket compression negotiation bug has been causing this. or at least, it was one of the reasons safari was broken with webwormhole.io. 2f6839e disables compression. it's live now. i only have access to test on safari 16 at the moment. it seems to work fine on both macos and ios. (safari still has issues with transferring large files efficiently, but that's different and has always been a problem.) i'll close this now, but if anyone still has issues with safari (especially safari 15, which is where this issues first started) please let me know and reopen. |
(the issue on the websocket package: coder/websocket#218) |
Just reporting that is works great on iOS 15.6.1! However, on mobile iOS 16.1.1, it doesn't work at all. |
oh dear! 16.0.3 works for me. upgrading to 16.1.3 now... |
@iamdoubz I couldn't reproduce this on iOS 16.1. Could there be anything else going on? Do you have Lockdown Mode enabled by any chance? |
I'm on iOS 16.2 and macOS 13.1 (Ventura) using Safari on both I cannot reproduce this either. Lockdown Mode is a good idea for a root cause☝🏻 |
Sorry for the dumb question, but what is "Lockdown Mode"? Is that webwormhole or iOS? |
It's a new iOS security feature: https://support.apple.com/en-us/HT212650 |
I see it. It is turned off, but I'm almost positive that my problem has nothing to do with this thread... I think you can close it. |
Steps:
open up webwormhole on macOS/Safari, also in parallel on a windows pc/chrome
create a new wormhole on osx
try to join it on windows
Safari page now says "Could not reach the signalling server. Refresh page and try again." with the follow console output:
Windows Page still says "connecting" with no relevant-looking console errors:
If I try to do this in the opposite direction (host on chrome/windows, join via safari/mac, Safari says "could not reach the signalling server:
Chrome looks to be just waiting passively and says in the console
[ If I try it with Chrome on both devices it works ok. I've noticed this issue for a while, fwiw, just only now had the energy to report. ]
The text was updated successfully, but these errors were encountered: