Some IOS apps not IPv6 ready? - ios

Apple requires that all apps in the app store to work in an all IPv6 network (no IPv4 network) according to this link
https://developer.apple.com/support/ipv6/
I was sniffing traffic from a few apps on the IOS and I checked to see if their APIs support IPv6 and it turns out that they don't. I checked their URLs on this site
http://ipv6-test.com/validate.php
I'm a bit puzzled about this. Aren't all apps in the Apple App store supposed to support IPv6?
One of the apps that I tested was the Textme app. Here is one of the URLs that they use within their app
https://api.textme-app.com/api/auth-token/
and by the looks of it, that domain does not support IPv6

The app needs to work in an IPv6-only environment with NAT64. That doesn't require the server to support IPv6, it just requires the app to not be bothered if the network pretends that the is reachable over IPv6-only.

Related

Apple App Store IPV6 Requirement

I am going to publish an app on Apple Store then I came to know about IPV6 rejection issue. My app only support for IPV4 and on this link I found that app should support IPV6.
So my question is that, Is it compulsory that app must support for both IPV4 & IPV6?
Sorry if looks as a foolish question but I am looking for a Apple link & more detail before getting rejected from Apple.
You don't need to worry about IPv6 support, if you've not set hard-core IPv4 IP address in your web server/service url connection.
This Apple document will help you: Supporting IPv6-only Networks
All apps submitted to the App Store must support IPv6-only networking. A majority of apps will not require any changes as IPv6 is already supported by NSURLSession and CFNetwork APIs. However, if your app utilizes IPv4-specific APIs or hard-coded IP addresses, you will need to make changes. Be sure to test for IPv6 compatibility before submitting your app to the App Store for review.
However, Apple guides in Testing your app in an IPv6-only environment:
You should test your app on an IPv6-only network. If you don’t have one, you can set up a test network by following the instructions in Test for IPv6 DNS64/NAT64 Compatibility Regularly.
Following SO reference, faced similar problem, may guide you:
IPv6 App Store Rejection

Please run your app on a device while connected to an IPv6 network (all apps must support IPv6) to identify the issue(s)

it might sound stupid but i have a problem: iTunes Connect rejected my app, claiming "We discovered one or more bugs in your app when reviewed on iPad running iOS 10.2 on Wi-Fi connected to an IPv6 network.". and they want me to: "Please run your app on a device while connected to an IPv6 network (all apps must support IPv6) to identify the issue(s), then revise and resubmit your app for review.".
Now, I understand that since 6/16 each app should supports IPv6. Because an application is just a software, i understand that they mean that each URL that I enter from my app should be accessible through IPv6. The weird part is that when i'm trying to reach sites which only available at IPv6 (like http://test-ipv6.com/, http://ds.testmyipv6.com/) i can't reach them, not from Android device, iOs devices, or from any mac. It's hard to believe that different ISP-s doesn't provide IPv6 support.
What am i missing here ?
Did any of you had that problem ?
Anything similar ?
It doesn't mean that servers need to be accessible through IPv6 (although it is highly recommended), it means that your application shouldn't care whether the server is IPv4 or IPv6. Some networks use NAT64 and DNS64 and will give your application IPv6 addresses even for servers that are only reachable over IPv4.
Apple's requirement is that your application must work in such situations.
This has been asked many times. Please look at previous answers. Here are some references:
Is Apple iOS defaulting to IPv6-only, on an app-by-app basis, in the real world?
Can't reproduce (IPv6?) connection issue that App Store review team is having

Required iPv6 compatibility - rejected by Apple iOS app

I uploaded my app on itunes multiple times and received the following message:
(
We discovered one or more bugs in your app when reviewed on iPhone running iOS 10.2 on Wi-Fi connected to an IPv6 network.
Specifically, when we attempted to create a new account a loading indicator spun indefinitely.
)
Apps are reviewed on an IPv6 network. Please ensure that your app supports IPv6 networks, as IPv6 compatibility is required.
Notes: I have used AFNetworking version 3.1.0 for call web services(support IPV6) and Apple Reachability(also support IPV6) without using hard coded Ip.
My question: the changes must be done on mobile side or server side?
As far as my experience with IPv6 reaches, you're probably right. When you develop your app in Xcode using the latest SDK for iOS 10.2, you should be save with IPv6 compatibility on your app's side.
However, Unix (MacOS audios are a Unix derivative) takes the path or url from your app and will negotiate at the OS level with the other side you want to connect with. This usually runs over a DNS. So, your app and iOS will first request an IPv6 IP address from the DNS. When the DNS understands IPv6, which is not always guaranteed, but it usually does, it asks the other side for an IPv6 address. If the other side does not support IPv6, the operating system will request an IPv4 address and set up the connection.
Since Apple will hold you responsible for the entire chain of services delivered by your app, you must ensure the requested side also supports IPv6 via it is part of the your apps functionality.
Hope this helps.

App Rejected with iOS IPv6 network

Yesterday, I submitted my app for review, but I got this message from Apple:
We discovered one or more bugs in your app when reviewed on iPad iPhone running iOS 9.3.2 on Wi-Fi connected to an IPv6 network.
Specifically, upon review we have found the application still experiences a loading issue and unable to review the application content.
My app uses ionic framework, how can I fix this problem?
I already used domain to access my server, but this problem still exists.
Yes. According to apple's policy , your application must supports IPV6. so, please check your application supports IPV6. Supporting IPv6 in iOS 9
To test, if your application supports IPV6 or not please check this ,
Supporting IPv6 DNS64/NAT64 Networks
To check with creating follow this steps , which indicate on apple's page .
To set up a local IPv6 Wi-Fi network using your Mac
1) Make sure your Mac is connected to the Internet(with ethernet), but not through Wi-Fi.
2) Launch System Preferences from your Dock, LaunchPad, or the Apple menu.
3) Press the Option key and click Sharing. Don’t release the Option key yet. (don't forget to press option key)
4)Select Internet Sharing in the list of sharing services.
5)Release the Option key.
6)Select the Create NAT64 Network checkbox.
7)Choose the network interface that provides your Internet connection, such as Thunderbolt Ethernet or Only Ethernet.
8)Select the Wi-Fi checkbox.
9)Click Wi-Fi Options, and configure the network name and security options for your network.
10) Select the Internet Sharing checkbox to enable your local network.
11)When prompted to confirm you want to begin sharing, click Start
12) Now your mac mini is working as a hotspot and useing IPv6 NAT64 network
(looks like above image when hotspot created)
Now connect your iphone with your mac mini's hotspot. and Test your Application it's working properly or not.
I hope this answer is helpful you.
Edit :- Don't forget to add below frameworks.
1) WebKit
2) CFNetwork
You will find all the information on this link related to ipv6 policy. Supporting IPv6 DNS64/NAT64 Networks
We also faced the same issue.
Just registered your website with any CDN like cloudFlare and your app will be approved next time no need to shift the whole site to any other server. This is the easiest way to get approval from app store.
I think Apple has something wrong with this error!
I have an app (ionic app) rejected 3 times (during Nov 2016) for the same error and lastly accepted without making any change related to IPv6!
You may need to check your app for startup errors if you think that you have nothing to do with IPv6.
By the way: I did not check IPv6 compatibility on my app, and even more the app - in its inner views - has a connection to a webpage that hosted on a shared host with no IPv6 support!!
Please note that sometimes the mobile app works in the test environment but not in the Apple own test environment. Following this and this link can be very helpful in determining what's the problem with apple rejections.
It is clearly stated that the test environment is not exactly the same

Is Apple iOS defaulting to IPv6-only, on an app-by-app basis, in the real world?

Apple's iOS App Store review process now includes a requirement that apps should work on IPv6 only networks.
With that in mind, is Apple defaulting to IPv6-only, on an app-by-app basis, for iPhones connected over mobile networks in the real world (not just in review)?
I.e. is Apple now forcing the move to IPv6-only in the real world for apps that pass it's IPv6 review?
(Any answer to the above question(s) would be great by itself, but for those with in-depth knowledge, a follow-up: Would UDP packets be properly routed to/from an IPv6 mobile device to an IPv4 server via NAT64 on the cellular network? It's actually this concern that leads me to the original question, I'm wondering if TURN clients are using TCP instead of UDP because UDP is not making it through IPv6->NAT64->IPv4).
Apple is not forcing IPv6 only support, but they have to adapt to what's happening in the world. More and more mobile networks deploy NAT64 and if apps on Apple would not work on those networks then that could give Apple a bad reputation. Therefore they require that apps support such a network.
There are still apps in the app store that have been uploaded before the IPv6 requirement was in place so they may be broken. At the moment those apps are allowed to stay in the app store, but in the future they might be kicked out. Last time I asked Apple hadn't decided over that yet.
UDP should work through NAT64, but it will be implementation dependent how long ports will remain open etc. That will depend on the network, not on Apple.

Resources