Was somebody able to work around this without socketrocket? is there still any way this will be fixed for the ios release?

Hi Matt, I filed bug report FB9616225. Creating a focused sample will be quite time intensive, so this might take a while. That said, I noticed that it manages to connect consistently after between 1 and 2 minutes. Meaning: I launch the app, websocket connection fails. With the app in the foreground, I wait 1 minute and it is still offline, but then it manages to connect before a second minute passes. Maybe that provides a useful hint? Thank you, Michi

Got it, thank you for your response. It will take a few days for us to produce a minimal test project. That said, I did find out today that while the connection consistently doesn't work initially, it does consistently succeed after 90 seconds of the app being in the foreground. Maybe that helps investigating the issue?

Is there any word on whether this will be addressed at some point? This is a big problem for our business and we don't really see a way to work around this (we tried different server side websocket configurations, but so far no luck). This used to work in iOS 14. Is there any way to configure the WKWebView to use the legacy code for now? Should we pull the app from the App Store for now? Is there any recommendation by Apple on how to handle this?