Search for a command to run...
App fails on IPv6-only networks because it hardcodes IPv4 addresses or uses networking libraries that don't support IPv6. Apple tests on IPv6-only.
7 cases reported · ~6 days to resolve
Apple's rejection message
Guideline 2.5.5 - Performance - Software Requirements: Your app does not work on IPv6-only networks. Please ensure your app supports IPv6 networking.
Replace all hardcoded IP addresses with domain names. Use high-level networking APIs (URLSession) instead of low-level socket APIs. Test using macOS Internet Sharing NAT64 network.
Guideline 2.5.5 - Performance. Your multiplayer games matchmaking server is unreachable on IPv6-only networks.
Fix: Updated game server to listen on both IPv4 and IPv6. Client uses getaddrinfo() for DNS resolution instead of hardcoded IPs. Tested matchmaking on IPv6-only network. All network calls use high-level AP...
Guideline 2.1 - Performance - Your app does not function correctly on IPv6-only networks. Several features failed to load during our testing.
Fix: Replaced all hardcoded IP addresses with domain names. Ensured DNS resolution works with both IPv4 and IPv6. Updated our networking layer to use URLSession which handles IPv6 automatically. Tested on...
Guideline 2.5.5 - Performance. Your apps payment processing fails on IPv6-only networks due to hardcoded IPv4 addresses in the payment SDK.
Fix: Updated payment SDK to latest version with IPv6 support. Verified all network calls use hostname resolution rather than hardcoded IPs. Tested complete purchase flow on IPv6-only network using Mac Inte...