And yet, AWS itself doesn't natively support IPv6 - you have to create a gateway for it. Grr. (Sorry for the off-topic rant)
I'm curious, how does Apple detect apps which don't support IPv6?
And yet, AWS itself doesn't natively support IPv6 - you have to create a gateway for it. Grr. (Sorry for the off-topic rant)
I'm curious, how does Apple detect apps which don't support IPv6?
Public ELBs support it. And even if you're only using one instance behind the ELB, its $14/month for that ELB. No one needs IPv6 on backend instances if they're only talking to the outside world through ELBs.
EDIT: I'm wrong.
> Load balancers in a VPC support IPv4 addresses only.
http://docs.aws.amazon.com/ElasticLoadBalancing/latest/Devel...
AWS is also used by plenty of smaller players who won't ever need more than one instance for everything. Or just devs who want a remote server to play with. Not everyone needs ELBs.
https://developer.apple.com/library/ios/documentation/Networ...
If their network is entirely IPv6 then they may not do anything special to test it. If an app fails with IPv4/IPv6 related errors then it doesn't support IPv6 properly.
If you're using the correct APIs with IPv4 addresses, you're fine.
"We will be reviewing on an IPv6 network, so if your app isn’t compatible with the IPv6 addressing, it may fail during review".
> At WWDC 2015 we announced that iOS 9 will support IPv6-only network services. All apps submitted to the App Store must support IPv6 starting in early 2016.