We have a mobile app on iOS (using Swift 2.3) that was submitted since October and in the stores ever since, recently (1 month ago) the app got rejected by Apple reviewer due to the fact that content is not loading when connected to an IPv6 network, they advise you to test it by connecting the app to an IPv6 network, and they have the documentation on how to set it up, which we did and when we connected the app to it the content are loading with slight delay (max 2.5 seconds).
Of course our back-end is on IPv4 network, but as even Apple states that should be no problem since the NAT64 translation happens.
We tried to talk to Apple to get more details but unfortunately its out of their process so they cant help us further.
Some of what we did is:
Monitored all traffic from mobile to back-end if any call happens
using an IPv4 address and not the DNS (because it will fail for an
IPv6), and all good, all goes out with the DNS name.
Checked the libraries used if there is a chance they are not
supporting IPv6 and nothing came up the list, all good.
We looked into the internet and we couldn't find a factor that might affect Apple's test, its working at our end on an IPv6 network but not at Apple's, we are trying to reproduce the issue with no luck, any information on this topic will be really really helpful as we have to submit the app to the store.
I have got rejections that read like this and the first time it scared me a lot just the trouble I'd have to go through to test it out, but in truth, they were only saying a screen didn't load for seemingly connectivity reasons. The screen wouldn't load on IPV4 either, but seems they didn't bother to test that much, and the bug was a very silly logic bug not related to IPV6 at all. Another time our prod server was busted at the exact time they tested. Try to figure out if that is not your case too before you get into specifics. You don't normally need to do anything special to support IPV6 if you're using the http networking libraries everyone uses nowadays.
Related
My app is working fine on IPad and Iphone when i am testing.I am using AFNetworking 2.0 for API's Calling and apple app review is Rejecting My App Again & Again due to IPv6 Network,i am Using Hard coaded Ip address like http://192.230.66.71/XXXXXXXX/XX/
i am frustrated to this,Please Anybody help me what to do now.
You are not supposed to use hard code IP address according to the Apple's rule.
Don’t Use IP Address Literals
Make sure you aren’t passing IPv4 address literals in dot notation to APIs such as getaddrinfo and SCNetworkReachabilityCreateWithName. Instead, use high-level network frameworks and address-agnostic versions of APIs, such as getaddrinfo and getnameinfo, and pass them hostnames or fully qualified domain names (FQDNs). See getaddrinfo(3) Mac OS X Developer Tools Manual Page and getnameinfo(3) Mac OS X Developer Tools Manual Page.
Note: In iOS 9 and OS X 10.11 and later, NSURLSession and CFNetwork automatically synthesize IPv6 addresses from IPv4 literals locally on devices operating on DNS64/NAT64 networks. However, you should still work to rid your code of IP address literals.
There are two things you should notice in my opinion:
1. Hard code IP address is not recommended, but according to the note above and the search I did that some developers pass the review with IPv4 address literals in their app.
So try not to use IPv4 address literals in your app first, then make sure you notice the second thing I mentioned following.
2. Your app could crash in other network related problems. Like what I comment before.
I will paste it here to make things more clear to you.
Make sure you handle the received data safely. My app was rejected in same reason but I found the real problem is the received data could be server error under some circumstances, which is resulted in crashing the app. I pass the app review by fix that bug.
For example, the app works fine under your network, but it could failed in other place like connection too slow and resulted in timeout. In that case, you will get some server error data or empty data, then if you force unwrap data in your code, the app will crash. And In my case, Apple rejected my app with IPv6 issues, which is not the real problem.
Our update has been rejected many times for ipv6 network connectivity issues. Our networking code has not changed between the previous release and this current release.
once i have just changed the testing credential which we gives apple for testing purpose and my application goes live.so now i am very much fed up with the things.because sometime apple accept and sometime its rejected.but he give the same reason due to ipv6 compatibility issue.
i have refer the apple documentation as well.any one can help me for this..
i have also search lots op link of stack overflow.
thanks in advance.
I have faced similar issue previously.
Steps you need to take care:
No IP Address should be hard coded.
Example: let api = 54.32.55.88 is invalid, use let api = www.mydomain.com
If you are using any Pods make sure they are compatible with IPv6.
Update the Reachability if you are using older.
Check your server configuration if its configured properly. Removing the AAAA if not valid for your configuration
If using AWS, AWS doesn't support IPv6, nor IPv6-only DNS through Route53.
Check some other solutions here.
Yes. I too faced this issue before many times. Apple is now supporting only apps those are compatible with IPv6.
First I tested my application as per their description. I tested on IPv6 but I didn't get any error as they said. So first complete debugging after connecting to IPv6. If you feel, it's working fine then do this.
I found out the IPVersion of my network through different websites. I took screenshots of the network I connected to on mobile and sent those screen shots to apple for review(saying it's a proof of connecting to IPv6).
Here below are the couple of sites that help you in finding out which version you are using.
Test IPv6
Google IPv6 test
Now it's accepted
As of June 1st 2016, all apps submitted to apple must be ipv6 compatible.
Here is the link for the announcement.
Now this comes with a lot of caveat. Basically this would take time to implement and apple started rejecting apps since September end. Now new apps that was being submitted was caught first, but now slowly apple is checking for ipv6 compatibility in old apps that owners are updating too.
Basically what apple tests is they connect their test device into a ipv6 network(their ISP broadcasts ipv6 connectivity), now if your app has a backend server, it should support any device that hits that server with ipv6 connectivity.
You can check whether your backend server is ipv6 compatible from here. Just paste your backend URL in the following and you will be able to see if your backend supports any ping from an ipv6 network.
If it doesn't then you have to make your server ipv6 reachable.
same issue was for me, if you are using Network Reachability class then update it from apple doc here.
Now my app is live with this fix.
I had same type of problem. I made an app which has a screen which only comes when a notification come so they(Apple team) could not able to check my app and giving me IPv6 issue then i told him about my app briefly that how my app works. So point only that tell him(apple team) about your app your problem can be solve.
I got an app rejection mail from apple which is below,
We discovered one or more bugs in your app when reviewed on iPad and iPhone running iOS 10.0.2 on Wi-Fi connected to an IPv6 network.
Specifically, app remains on splash screen upon launch.
Based on their request i have created the NAT64 network on my Mac and shared that internet for the iPhone 5S device 10.0.2 os version , App was working fine,
But apple says its not working with IPv6
Can anyone confirm that do i need to check anything else?
Related question
Environments:
Appcelerator Studio Ti SDK 5.1.0 GA
XCode Version 6.3
Thanks in advance
Just Read the mail you got from apple people. Answer will be there only.
Use wireshark to know what exactly your network doing.
Also to understand the problem better use wireshark for analyzing what is going on - create an network as outlined in that session and see what happens on the wifi port
https://developer.apple.com/videos/play/wwdc2015/719/
for more info check #Sean Answer
After quite a bit of stress, I can confirm that the issue was a problem with our backend not being correctly configured for IPv6. Apparently, AWS doesn't support IPv6, nor IPv6-only DNS through Route53. I ended up moving all the internet facing bits of the backend away from AWS for the time being. I wanted to leave this up because I think there are probably going to be others who find themselves with similar problems as people start submitting updates past the IPv6-only restriction. The best tool I found for testing server/dns readiness has been: http://ready.chair6.net/
Request your hosting provider to assign your server IPv6 as well and they will not charge you for this. This will resolve your IPv6 issues.
In my case I contacted the hosting provider about this issue and they said IPv6 is not assigned to my server I requested them and asked for the cost, they said it is free of cost and will assign it now. I think hosting companies have to assign IPv6 to all servers but they are assigning it on priority bases for those who are facing this issue.
So better you contact hosting provider for your IPv6 assignment.
My app got rejected with message from Apple as "Your app crashes on iPad running iOS 10.0.2 connected to an IPv6 network.” and also did not get anything from the crash log attached. Please reply whoever resolved this issue.
Actually I am getting server not found error whenever trying to access the api server from ipv6 only network. My api server only supports ipv4 network. Do I need to change anything in api server? Can anyone post any sample code to access api server using NSUrlConnection object that support the ipv6 only network?
If you are using AFNetworking library or Apple's Reachability class, updating your classes, than problem solved.
Don't get confused by that message. I got that too but the problem is not necessarily caused by the IPv6 Network. My feeling is they just write this always even if the error is something else. I had this with an app myself last week but the error was just a completely different reason. Maybe you just look into your code where the problem occurred. They probably wrote at which point in your app it crashed.
App is now approved by the apple review team after increasing the target version to 9.2 previously it was 8.1.
A lot of server environments have not started supporting IPV6 (Think Azure in some configurations). This causes the scenario where the api being used by the app are not useable. Do handle such scenarios in your code.
Apple's own reachability class and some other third party frameworks use low level apis/sockets for their own purpose. These are the problematic areas.
Most of the High level code using NSURLConnection is ok, but if you are using any third party libraries or older versions of AFNetworking, you'll need to check if they are using any sockets. If they are, then look for options/upgrades.
We faced the same issue recently, ended up with lots of fixes to server and third party libs in the app.
I have created an iOS VOIP app. The reason behind creating a VOIP app was to make my application run in background. Well that is working fine. I am also connected to a host through TCP/IP.
The problem here is when the OS is restarting the wifi radio automatically at some interval, which results in a disconnection. Then I have to reconnect.
Can anyone help me to understand what exactly is causing this behaviour?
There are a few things this could be. Firstly, are you running iOS 8? there have been some reported wifi issues with it. Just google iOS 8 wifi issues to see how many people are having similar issues.
Secondly, it's not too irregular for your wifi network to shuffle you around, so it could be either your wifi router itself, or the iPhone. I would probably try using manual ip allocation instead of DHCP on your router as a test.
Thirdly, your software obviously needs to be set up to handle dropouts etc - dropouts and package less etc are fairly common parts of any networking.