Since posting the ticket we learned that Boost Beast using an Async Secure WebSocket (WSS) simply times out. Secure Synchronous WebSocket connections work fine. The issue is specifically related to new iOS releases. Any ideas what would have changed between iOS 18.1 and 18.3 that would affect Boost Beast Secure Async WebSockets from working correctly? Or perhaps something was changed in how memory or threading is managed in the new iOS releases?

Yes Boost Beast and specifically the secure async websocket connection times out but not the async for iOS 18.3.x. The same exact C++ library wrapped with the framework has no problems with secure async websocket connections on iOS 18.1.x. LibDataChannel's secure async websockets works fine on iOS 18.3.1. So the problem is related to how Boost Beast implemented secure async websockets and iOS 18.3.1.