required iPv6 compatibility – iOS app rejected by apple

by

If you are using IPv4-specific APIs or hard-coded IP addresses, you will need to update your code, Although all NSURLSession and CFNetwork APIs(including NSURLConnection) already support IPV6

As mentioned by Apple:

At WWDC 2015 we announced the transition to IPv6-only network services
in iOS 9. Starting June 1, 2016 all apps submitted to the App Store
must support IPv6-only networking. Most apps will not require any
changes because IPv6 is already supported by NSURLSession and
CFNetwork APIs.

If your app uses IPv4-specific APIs or hard-coded IP addresses, you
will need to make some changes.

Although. Apple also recommends not to use IP Address Literals, for long term (Not necessary)

Don’t Use IP Address Literals

Make sure you aren’t passing IPv4 address literals in dot notation to
APIs such as getaddrinfo and SCNetworkReachabilityCreateWithName.
Instead, use high-level network frameworks and address-agnostic
versions of APIs, such as getaddrinfo and getnameinfo, and pass them
hostnames or fully qualified domain names (FQDNs). See getaddrinfo(3)
Mac OS X Developer Tools Manual Page and getnameinfo(3) Mac OS X
Developer Tools Manual Page.

Note: In iOS 9 and OS X 10.11 and later, NSURLSession and CFNetwork
automatically synthesize IPv6 addresses from IPv4 literals locally on
devices operating on DNS64/NAT64 networks. However, you should still
work to rid your code of IP address literals

If you are using AFNetworking Library, Please make sure to update it to version above 3.x, as they seem to have updated few of the things. –> AFNetworking Added support for IPv6 to Reachability.

For Detailed Info, please follow this link

Supporting IPv6-only Networks

ALSO, TO TEST

You can follow this detailed tutorial:

tutorial-how-to-test-your-app-for-ipv6-compatibility

More Related Contents:

  1. Submit to App Store issues: Unsupported Architecture x86
  2. Xcode 7 error: “Missing iOS Distribution signing identity for …”
  3. How to get my IP address programmatically on iOS/macOS?
  4. Validation Error: Invalid Bundle. The bundle at … contains disallowed file ‘Frameworks’
  5. App rejected due to missing usage descriptions (Xcode8)
  6. Unexpected CFBundleExecutable key
  7. My prerelease app has been “processing” for over a week in iTunes Connect, what gives?
  8. Invalid Swift Support / invalid implementation of swift
  9. App “does not contain the correct beta entitlement”
  10. change app name in App Store
  11. This action could not be completed. Try Again (-22421)
  12. IPv6 App Store Rejection
  13. You are not authorised to use this service iTunes app upload error [closed]
  14. Which iOS app version/build number(s) MUST be incremented upon App Store release?
  15. Missing CFBundleIconName in Xcode9 iOS11 app release
  16. ITSAppUsesNonExemptEncryption export compliance while internal testing?
  17. Build not visible in itunes connect
  18. CFBundleVersion must be higher than previous version
  19. Ad-hoc Deployment
  20. “Too many symbol files” after successfully submitting my apps
  21. App Store Connect message: Your account will soon need to be migrated to federated auth
  22. xcode 6 upload app with error: iTunes Store operation failed Error Description not available
  23. ITMS-90809: Deprecated API Usage – existing app that use UIWebView are no longer accepted
  24. An error occurred uploading to the iTunes Store
  25. Invalid Signature (Invalid Binary) on iTunes Connect
  26. Customize apps gallery in appstore page
  27. Images can’t contain alpha channels or transparencies
  28. ERROR ITMS-9000: “Redundant Binary Upload. There already exists a binary upload with build version ‘1.0’ for train ‘1.0’”
  29. Changing root view controller of a iOS Window
  30. How can I delay a method call for 1 second?

Leave a Comment