We submitted cordova phonegap app to apple and it was rejected saying that our app does not support ipv6. This is the first time we are getting this error and not sure on exact steps for fixing this issue.
Our app is using amazon ec2 and we noticed that amazon ec2 is not supporting ipv6. So we want to know where do we need to fix this? In the amazon or inside the app?
If it is amazon, how we can fix it? we tried to fix amazon issue by adding ELB but it has not solved the problem yet.
We are using latest version of cordova and all libraries are latest version. Please let us know
This is not an issue related to your webservice/webserver.
Since this June, Apple expects Apps to run on IPV6 networks. Apple has started rejecting Apps which do no comply with this.
NSURLSession, NSURLConnection, AFNetworking 3.x+ all support IPV6
If you are using any other network libraries, please use below link to test IPV6 support
http://www.brianjcoleman.com/tutorial-how-to-test-your-app-for-ipv6-compatibility/
If you come across issues in making web requests when your App is running on an IPV6 network, you will have to update/replace your networking libraries to IPV6 supporting equivalents.
Once you are done testing your App with IPV6 support, you can re-submit it to the app store for approval.
Related
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 have uploaded my app to Apple store. I am using iOS 10.2. After upload, I got a rejection message:
Your app crashes on iPad and iPhone running iOS 10.2 connected to an IPv6 network when we:
Specifically, we found that the app crashes after sending messages on Wi-Fi
How can I solve this?
If you app contains webservices and you have implemented NSURConnection then please convert all NSURLConnection to NSURLSession . .
My App got rejected for the same reason, but it was not the issue. The reason my app got rejected because it got crashed on login button click.
It was working when i compile and run with xcode (ie xcode 8.2.1) but apple said it was crashing.
So i tried running it in release mode because we usually run our app in debug mode when we run on xcode.
from
to
And my App crashed when i ran it on release mode and i found the bug, it happened when the compiler tried to optimise a decryption function.
I think there is some issue with the new llvm 8.0 compiler.
Now my App got even approved by AppStore.
The answer is fairly simple, you're going to have to try and reproduce the crash and fix it.
Apple won't let apps into the App Store of which it finds crashes for. I'd recommend finding a friend/family member who has an IPv6 enabled network (if you can't enable it yourself) and attempting to use your app in various conditions under that network.
The App Review network, like the networks deployed by service providers, does support IPv6-to-IPv6 connectivity. Thus, if your server supports IPv6, your app will talk to it directly, without going through the NAT64 translator.
Please check your link is support ipv6 or not use this LINK
and read more
Just add a CDN (Example: Cloudflare) to your domain, change nameservers accordingly and make sure IPv6 compatibility feature is turned ON. This worked for me
After June 1, I submit my ionic app to iTunes connect and I got the message from apple.
Apps are reviewed on an IPv6 network. Please ensure that your app supports IPv6 networks, as IPv6 compatibility is required.
I have used AFNetworking version 3.0 for API call.
and I am not using the hard coded IP Address in my app to call API. I have used http://www.xxxx.com/API/login.php
So now, what I have to change on mobile side and server side?
Please help me to find out the solution for the same.
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.