Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

App store Rejects App for IPV6 network support on iOs 10

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

like image 267
Silambarasan Raman Avatar asked Oct 05 '16 10:10

Silambarasan Raman


People also ask

Can Iphone connect to IPv6?

All Apple operating systems support IPv6, implementing several mechanisms to protect the privacy of users and the stability of the networking stack.

Why does my Iphone say app not supported?

It's possible that you're trying to update an app that is out of date and no longer supported by iOS. Try downloading a different app to see if this is what's causing the update to fail. Try searching for the app in the App Store, if it isn't showing up it's likely that it's been removed.

How do I allow apps to run on iOS?

For iOS Devices If Background refresh is greyed out in the ON position, go To Settings App - > General - > Background App Refresh - > Turn on the option for the system, and then you can turn on / off by app.


1 Answers

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/

like image 160
Deepak Carpenter Avatar answered Oct 20 '22 06:10

Deepak Carpenter