Apple pushes IPv6, does your app conform to the new rules?

May 4, Apple announced a new rule: since June 1, all applications must support the Ipv6-only network. Apple said Apple had proposed a transition to ipv6-only network services as early as the 2015 Apple Global Developers Conference, and provided support for IPV6 api:nsurlsession and Cfnetwork. Therefore, most applications do not need to make changes. Netizens from Hacker News had a lively discussion of Apple's behavior, even though the title meant a little more than a headline that "Apple forbid app only supports IPV4" to help you understand. They expressed support for Apple's behavior and expressed concern about the obstacles IPv6 had encountered in the promotion process. The most notable thing for developers is whether their application conforms to Apple's new rules. StackOverflow's Netizen "Dgatwood" lists the following questions about how to quickly determine whether an app supports IPV6: is the IP address used directly? Do you want to allow the user to enter the address directly in some form other than the URL? Are you using an API that is not based on Nsurl? Are DNS lookups made directly for some reason? Dgatwood that, in response to these questions, if your application gives the answer "no," then there is no need to make any changes to support IPV6. In addition, he suggested the use of AFN 3.0 and later version of the network framework, but also in the use of ASI developers have to be careful, although it may still be normal use, but because the ASI has stopped the update, it is not suitable for iOS9, so StackOverflow netizens think, This framework for stopping updates should not be used. As we all know, with the rapid development of the Internet, IPv4 was replaced by IPV6 has become an inevitable trend. However, due to many reasons, the promotion of IPv6 is not very smooth. Apple's behavior is undoubtedly a IPv6, accelerating its replacement of IPv4 pace. The most notable thing for developers is whether their application conforms to Apple's new rules. StackOverflow's Netizen "Dgatwood" lists the following questions about how to quickly determine whether an app supports IPV6: is the IP address used directly? Do you want to allow the user to enter the address directly in some form other than the URL? Are you using an API that is not based on Nsurl? Are DNS lookups made directly for some reason? Dgatwood that, in response to these questions, if your application gives the answer "no," then there is no need to make any changes to support IPV6. In addition, he suggested the use of AFN 3.0 and later version of the network framework, but also in the use of ASI developers have to be careful, although it may still be normal use, but because the ASI has stopped the update, it is not suitable for iOS9, so StackOverflow netizens think, This framework for stopping updates should not be used. As we all know, with the rapid development of the Internet, IPv4 was replaced by IPV6 has become an inevitable trend. However, due to many reasons, the promotion of IPv6 is not very smooth. Apple's behavior is undoubtedly a IPv6, accelerating its replacement of IPv4 pace. This address: Http://www.linuxprobe.com/ipv6-app

Apple pushes IPv6, does your app conform to the new rules?