简体   繁体   中英

My ios app got rejected due to ipv6 network issue

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?

如果您正在使用AFNetworking库或Apple的Reachability类,则更新您的课程,而不是解决问题。

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.

应用程序现已获得苹果审核小组的批准,目标版本增加到9.2之前为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.

The technical post webpages of this site follow the CC BY-SA 4.0 protocol. If you need to reprint, please indicate the site URL or the original address.Any question please contact:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM