Sure enough, Apple made a big move, and the iOS industry was thrown into a storm. Last May, Apple announced that all developers must submit an updated version of their apps by June 1st to support IPv6-only networks. This triggered a wave of research across the developer community, as everyone started investigating which parts of their apps were not yet compatible with IPv6.
Apple’s App Store policy now requires all iOS apps to be compatible with IPv6-only networks. Starting from June 1st this year, any app submitted to the Apple App Store must support the latest internet protocol for hardware identification and network routing — the IPv6-only standard. This requirement was first introduced at the 2015 Apple WWDC Developer Conference, and iOS 9 was the first to begin transitioning to IPv6-only network services.
According to the Apple Developer website, most existing apps are already compatible with NSURLSession and CFNetwork APIs. However, developers who still use IPv4 APIs or hard-coded IP addresses will need to update their code to meet Apple's new requirements. With the exhaustion of IPv4 addresses, the shift to IPv6 has become increasingly important. For Apple, moving to IPv6 will not only enhance industry acceptance but also support the continued growth of the Internet of Things and ensure the long-term health of smartphone ecosystems.
**What is IPv6-Only?**
Previously, most people used IPv4, where IP addresses looked like 114.255.40.66. However, due to the limited number of IPv4 addresses, IPv6 was introduced. IPv6 addresses look more complex, such as 2001:da8:215:4009:250:56ff:fe97:40c7.
Currently, network cards often support both IPv4 and IPv6 addresses. In the future, devices may only have IPv6 addresses. While devices using different protocols can't communicate directly, there are transition techniques like DNS64/NAT64 that allow them to access each other in certain scenarios.
In practice, when connecting to Wi-Fi, 4G, or 3G networks on iOS devices, you're typically assigned an IPv4 address. However, as carriers and enterprises gradually deploy IPv6 DNS64/NAT64 networks, devices will start receiving IPv6 addresses instead. These IPv6-only networks can still access IPv4 content through the DNS64/NAT64 infrastructure.
Here’s how it works: When a client requests domain name resolution, the DNS64 server first tries to find an IPv6 address. If it fails, it queries the DNS server for an IPv4 address. The DNS64 server then synthesizes an IPv6 address and returns it to the client.
On a Mac OS 10.11+ dual-NIC machine (Ethernet + Wi-Fi), you can simulate an IPv6 DNS64/NAT64 environment to test if your app supports IPv6-only networks. Here’s the setup:
**How to Meet Apple’s Requirements?**
Apple’s requirements are manageable for most developers. Most apps today don’t need to change anything to meet the standards. However, if you're unsure, here’s what you should do:
- Use domain names (like example.com) instead of hardcoding IPv4 addresses (like 114.255.40.66).
- Ensure your server has a public IPv4 address and a fully qualified domain name (FQDN).
**Does Your Server Have an IPv6 Address?**
No, your server doesn’t need an IPv6 address. As long as it has a public IPv4 address and a domain name, it can work with IPv6-only networks through DNS64/NAT64.
**How to Create an IPv6-Only Test Environment?**
MacOS provides tools to help you create a local IPv6 DNS64/NAT64 network. You can share your wired connection over Wi-Fi and enable NAT64 to simulate an IPv6-only environment.
**How Does Apple Review Support for IPv6-Only?**
First, supporting IPv6-only means your app should function correctly on DNS64/NAT64 networks. However, since most current networks are still IPv4-based, your app must remain functional in both environments.
Apple won’t reject your app just because it uses IPv4 APIs, as they may coexist with IPv6-compatible APIs. But to reduce the risk of rejection, it's better to replace outdated IPv4 APIs with IPv6-compatible ones.
Second, starting with iOS 9, Apple began supporting IPv6. In iOS 9.2 and later, the `getaddrinfo` method can synthesize IPv6 addresses from IPv4 literals. The Reachability library in iOS 8 may not handle transitions between IPv4 and IPv6 well, but Apple says only IPv6 compatibility is required on the latest systems.
Third, as long as the main functionality of your app supports IPv6, it should pass Apple’s review. Modules that aren’t fully IPv6-ready may take time to affect users, but eventually, they’ll need updates.
Fourth, if your app uses direct IPv4 addresses in `NSURLConnection` or `NSURLSession`, it might still work on iOS 9 and above in IPv6 networks. However, it won’t work on iOS 8.4 and below. Apple recommends removing hardcoded IP addresses from your code, even if it works now.
In summary, while the transition to IPv6 may seem daunting, it’s a necessary step for the future of the internet. Apple’s move ensures a smoother, more scalable network for both developers and users.
Barium titanate lead-free piezoelectric ceramics are important basic materials for the development of modern science and technology, which was widely used in the manufacture of ultrasonic transducers, underwater acoustic transducers, electroacoustic transducers, ceramic filters, ceramic transformers, ceramic frequency discriminators, high voltage generators, infrared detectors, surface acoustic wave devices, electro-optic devices, ignition and detonation devices, and piezoelectric gyroscope and so on.
Application:Â Â ocean, fishery, scientific research, mine detection, daily life and other fields.
Piezo Disc,Piezo Rod,Lead Free Piezo Rods,Lead Free Piezo Discs
Zibo Yuhai Electronic Ceramic Co., Ltd. , https://www.yhpiezo.com