Posts

Post not yet marked as solved
4 Replies
0 Views
Thanks for your answers Eskimo. I will keep digging in this area, this is quite important for my Apps and maybe ask this at WWDC 22 if will be sessions on Networking area. I will post here if get more info that might help the community in this matter. Thanks, Florin Angry Software
Post not yet marked as solved
4 Replies
0 Views
Thanks for answer eskimo ! I believe you’re bumping into the limitation discussed in Low-Level Networking on watchOS. The issue that is if i do the connection to the server with ip and port directly everything works well. connection?.currentPath?.remoteEndpoint has correct data. Do you know if there is any new news of low-level networking on WatchOS or if there is any plan to fully support all network framework features for WatchOS ? Thanks, Florin Angry Software
Post not yet marked as solved
5 Replies
0 Views
Hi Eskimo, Thanks for your example. This works great on Simulator but on Real Device i always get only IPV6 address for the same code base and the same server. Do you know what can be the reason ? Btw: Instead of direct ip/port for connection i'm using a NWEndpoint that is created by a NWBrowser .bonjour instance and listening for browseResultsChangedHandler from where i get NWEndpoint . Any idea why ? Thanks!