Hi, everyone
Hi, everyone
Im using indy component to connect to api / services on my mobile application.
To send my application to AppStore , application has to support IPV6.
I trid to set IPVersion property to IPV6 for IdHTTP component but it didnt solve.
Did anyone face that problem , or any idea to solve it?
You can find the anouncement of the apple that wont support IPV4 anymore.
https://developer.apple.com/news/?id=05042016a
https://developer.apple.com/news/?id=05042016a
Im using indy component to connect to api / services on my mobile application.
To send my application to AppStore , application has to support IPV6.
I trid to set IPVersion property to IPV6 for IdHTTP component but it didnt solve.
Did anyone face that problem , or any idea to solve it?
You can find the anouncement of the apple that wont support IPV4 anymore.
https://developer.apple.com/news/?id=05042016a
https://developer.apple.com/news/?id=05042016a
When I call if gstack.SupportsIPv6 then .... I tested with all OS ..win32 ..ios and android
ReplyDeleteRyan Pfeifle It's possible that checking for IPv4 addresses isn't going to be sufficient. I'm in the process of testing this, and my device still has an IPv4 address on one of the interfaces despite me having turned off cellular data, bluetooth (just to make sure) etc, and its wifi is connected to my Mac's shared NAT64 (IPv6 only) network. It looks like the only way to be sure is going to be to test the target host by resolving the address and see if it comes out as an IPv6 address?
ReplyDeleteRyan Pfeifle I hadn't progressed as far as finding out which interface had the IPv4 address: it was one of lo0, en0, awdl0 or utun0. My guess is that it's because, while testing, I have the USB cable connected to the device; I'll find out for sure later today. I noticed also that the routine for retrieving local addresses is broken for IPv6 addresses: they come out as blank (at least they did on my device). Is there some reason that inet_ntop is not being used?
ReplyDelete