IPv6 App Store拒绝 [英] IPv6 App Store Rejection

问题描述

我们的更新今天因ipv6网络连接问题被拒绝两次。我们的网络代码在之前的版本和当前版本之间没有变化。

Our update has been rejected twice today for ipv6 network connectivity issues. Our networking code has not changed between the previous release and this current release.

该应用程序仅向api.metooapp.io发出https网络请求，该请求已正确配置为ipv6 [ 0 ]并在AWS上的route53后面运行。代码中没有硬编码的IP地址。

The app only makes https network requests to api.metooapp.io, which is correctly configured for ipv6 [0] and runs behind route53 on AWS. There are no hard-coded IP addresses in the code.

即使按照[ 1 ]这是拒绝通知中提供的链接。看起来我不是唯一遇到此问题的人，[ 2 ]。

I am unable to reproduce this issue, even after following the steps to create an ipv6 network at [1] which is the link that was provided in the rejection notice. It looks like I'm not the only one experiencing this issue, either [2].

推荐答案

经过一番压力之后，我可以确认问题是我们的后端没有正确配置IPv6。显然，AWS不支持IPv6，也不支持通过Route53支持IPv6的DNS。我最终将所有面向后端的互联网部分从AWS移开了。

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.

我想放弃它，因为我认为可能会有其他发现自己遇到类似问题的人开始提交更新超过仅限IPv6的限制。我发现用于测试服务器/ dns准备情况的最佳工具是： http://ready.chair6.net/

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/

这篇关于IPv6 App Store拒绝的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！