![]() Wait for like 15 minutes (you need to give it some time to happen, it won't fail if you wake up the computer right away).Ĥ. Open a campfire in Basecamp (you can create a free account in )ģ. ![]() Today, I was able to also reproduce the problem with Safari Technology Preview release 135 (macOS Monterey):ġ. Disconnecting the wifi, trying to send a message, and connecting it again fixed the issue. I tried to debug the problem with Safari dev tools, with my unit plugged, and closing the web sockets and creating new ones from the console wouldn't fix the problem either.ģ. The app embeds a WKWebView instance, and reloading the page there won't fix the problem. The only way to fix is restarting the app. It happens intermittently when restoring the app from the background.Ģ. > WebSocket connection to 'wss://xxx' failed: WebSocket is closed before the connection is established.ġ. The cause is that the underlying web sockets fail to connect with the same error: We got several reports from customers about this. We have been experiencing this bug in our Basecamp iOS app since the upgrade to iOS 15: when opening a chats and trying to send a message, it would sometimes fail to deliver it. I could reproduce the problem exactly as described by Matt Windwer in. Please let me know if I can provide any further details to help in the investigation, or if a new bug report needs to be filed, and I will be happy to help in any way I can. I hope that this helps demonstrate the issue at hand. Please ignore the Basic Auth prompts in the video as that is just for the JavaScript source maps since the web inspector is open. Re-enabling "NSURLSession WebSocket" kills the connection again, in perpetuity, until it is disabled. Reloading the page works fine with "NSURLSession WebSocket" disabled.ĥ. After disabling "NSURLSession WebSocket", the connection is established immediately.Ĥ. After reloading the page, the connection still cannot be established.ģ. Computer has woken from sleep after some time, and WebSocket connection (via the /cable endpoint) can no longer be established (client-side code continues to retry every 6 seconds).Ģ. I have attached a screencast demonstrating how WebSockets becomes broken on our website, even after reload, with "NSUrlSession WebSocket" enabled when the above scenario occurs on Safari Technology Preview 135 using my M1 MacBook Air. We are pretty sure this bug is also in Safari for iOS 15.x (including 15.1) based on customer reports. Disconnect from WiFi and then reconnect (no need to exit Safari). ![]() In order to resolve this, we have found that the user needs to do one of two things:Ģ. Even reloading the website no longer establishes a WebSocket connection. Return to the laptop, and when it awakens, Safari loses the ability to connect to WebSockets completely on our website. Walk away from the laptop (letting it sleep) for some time.ģ. Visit our website, which establishes an active WebSocket connection to our server.Ģ. Alex, we are able to reproduce an issue on Safari 15.1 for Mac as well as the latest Safari Technology Preview Release 135 where "NSUrlSession WebSocket" (which is enabled by default) is breaking the ability to connect to our server at all using WebSockets after the computer sleeps in the following scenario:ġ.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |