User Profile

Note that seems to be the same issue as https://forums.developer.apple.com/message/189470#189470 which never appeared to have a resolution.

Hi,Thank you very much for testing this out and sorry for the super late response. Only now have I gotten time to look into this again.Really strange that this works for you. Unfortunately, it seems to be an issue across many devices on our side. I tried connecting my iPhone XS to 3 different Macs (2 x 2017 MBPs and a 2015 MBP) with Internet Sharing enabled, all 3 of them had the same result in the Xcode window:--unspec--ai_flags:0 ai_family:2 ai_socktype:1 ai_protocol:6 ai_addrlen:16 ai_canonname:IP address: 93.184.216.34--inet6--ai_flags:0 ai_family:30 ai_socktype:1 ai_protocol:6 ai_addrlen:28 ai_canonname:IP address: ::ffff:93.184.216.34I also tried running this on a different iPhone 7 in case there's a configuration error on their side, and again, it came up with the same output in Xcode.Unfortunately, this is blocking us from getting IPv6 to work correctly with some internal networking code. We made sure to follow https://developer.apple.com/library/archive/documentation/NetworkingInternetWeb/Conceptual/NetworkingOverview/UnderstandingandPreparingfortheIPv6Transition/UnderstandingandPreparingfortheIPv6Transition.htmlto the letter to set up the the MacNAT64.Looking at the man pages for getaddrinfo, I noticed the following sentence:"On non-qualifying interfaces, getaddrinfo() is guaranteed to return immediately without attempting any resolution, and will return the IPv4 address if ai_family is PF_UNSPEC or PF_INET."This appears to be what is happening on my side. Is there a syscall that we can use (or some logs we can look at) to investigate why the interface may be non-qualifying (or check whether that's the case)?I'm beginning to think that perhaps my Xcode project is misconfigured somehow? I'm not doing anything except using the Xcode managed provisioning profile with my developer account, with default settings created from the "Single view app" template, and using the code in this thread.Do you have any further insight into debugging this, or maybe seeinfg whether the MacNAT64 is doing the right thing? Could it be caused by our internal network? I'll try the same test again at using a different network (my home wifi) as well to see if that changes anything.EDIT (5/6/2019): I tried on a different network, and my colleague also tried building an Xcode project on a different laptop (rather than just running the NAT64 gateway on a different laptop), and still no change. I'm suspecting at this point that perhaps the Xcode project setup is to blame, as I can't think of any other variables which are different between our setup and yours @eskimo.Thanks again