If the iOS application is successful in working across the macOS NAT64 test environment, then the next step is to submit a bug report. We ask developers to use the Apple Developer Bug Report web page - http://bugreport.apple.com to submit the bug report. The bug report is to indicate that there is some compatibility issue between the app and the App Review test environment. In the bug report, the developer provides evidence that the iOS application worked successfully across the macOS NAT64 test environment by including a packet trace to show the success of the connection process.

Note that the bug report is not an indication as to where the problem lies, but the fact that the iOS app works in the test environment and not in App Review is an indication that the app / App Review interaction needs further review. Once the bug report is submitted, there issue is then assigned to investigation by an App Review group. Once a bug report is assigned to App Review, the next thing is to follow up with the bug report by communication with App Review - “[email protected]”. While the email inquiries may not always get a response - all of the correspondence is viewed.

Cloud and Server

The Photon Cloud can not provide public IPv6 addresses in the short term. However, Apple's requirement is only that clients can cope with IPv6 addresses in their network, if that provides "IP translation", as described in their article.

For anyone using Photon Server (OnPremise), this means, you can likely continue to run it as IPv4 service.If you want to setup a true IPv6 server, we have some docs for that.

I was looking for new requirements from apple and didn't find any. So, as long as you followed the instructions above, your app should be fine and pass.

What I found is, that a few other developers also failed to pass through IPv6 checks and they resubmitted or escalated the cases. After some back and forth, their apps went through certification - often without changes!

This is stated in Xcode:Connect() to '184.173.132.27' failed: System.Net.Sockets.SocketException: Network is unreachable at System.Net.Sockets.Socket.Connect (System.Net.EndPoint remoteEP, Boolean requireSocketPolicy) [0x00000] in :0 at ExitGames.Client.Photon.SocketTcp.DnsAndConnect () [0x00000] in :0 ExitGames.Client.Photon.SocketTcp:DnsAndConnect()

You need to have DNS entries for all servers and set the Hostname for each. Make sure you have the minimum required server version for this.Once setup, the client will get hostnames instead of IPs. Then it can resolve that name to a IP and connect.

Using PUN 1.75 and Unity 5.4.0p3 and Apple is rejecting my app for IPV6 compatibility. Works on NAT64 and IPV4 networks but not on whatever they're using. Any suggestions for what to look for in order to ensure it works for them? I've read the IPV6 pages and nothing jumps out as something I've done differently.

I updated my submission to include your suggestions above and they approved the same binary they'd previously rejected. It does pass the NAT64 test when I test it on my own but I can see in the logs I gather that they have problems getting into a multiplayer match... so, I'm not sure what/why... but they seem to at least be aware that a problem exists.

@Carter, I updated the first post in this thread for help and info. As you can see in the post above yours, SMartin's game was first rejected and then got accepted after pointing out that it was in fact tested against Apple's own guide.

If you tested, please get in touch with the reviewer crew and let them know. If possible, update us later on.

I am using 4.1.3.3 native C++ sdk instead of PUN. i am having the same issue that our app passed our own IPv6 test according to Apple's own guide. However, App Review test keeps failing. App Review team can connect to our lobby server but failed to connect to game server when joining a game room.

once you get the rejection, as long as you appeal and point out that you have tested according to Apple's IPv6 page, then they will approve it even though the 2nd time testing will still fail for them.

The app will be approved, however it means ur app will take extra time to get approved. and because of the IPv6 issue, all your software update will be rejected, then appeal, then approved. we have submitted 2 subsequent software updates, all of them are first rejected due to IPv6 issue, and then later approved after we appeal.

This is quite annoying going forward. I am currently working with a Apple Developer Technical Support to try to get this issue sorted out. He recommended us to file a bug report against App Review, and attach Wireshark packet trace to show that our own testings are indeed passed in IPv6 environment.

@KevinB: Thanks for the info! This is really annoying and a waste of time. Very cool you are trying to figure out why and how things fail for them. We and a lot of other developers test with Apple's setup and we can't get why they fail.

Apple message." As we discussed, it would be appropriate to revise your app and make sure it supports IPv6 networks and that the IAP products are implemented correctly. We discovered one or more bugs in your app when reviewed on iPad and iPhone running iOS 9.3.5 on Wi-Fi connected to an IPv6 network.

@KevinB: Thanks for the info! This is really annoying and a waste of time. Very cool you are trying to figure out why and how things fail for them. We and a lot of other developers test with Apple's setup and we can't get why they fail.

@KevinB: Thanks for the info! This is really annoying and a waste of time. Very cool you are trying to figure out why and how things fail for them. We and a lot of other developers test with Apple's setup and we can't get why they fail.