iOS App rejected due to IPv6 error

We are facing the same issue with Unity 2017.3.1p1, is there a new patch release resolving this issue?

 

Looks like the IPV6 was not the issue at all, I don't know why they keep saying that the app crashed using ipv6 network. once my app doesn't even connect to the internet, so I asked them what they did to produce that error "Your app crashed on iPad or iPhone running iOS 11.2.5 connected to an IPv6 network during our review." and they answered me with this:



"We noticed that several screens of your app were crowded or laid out in a way that made it difficult to use your app.

Please see attached screenshots for details. These screenshots represent some examples of this problem but may not represent all instances of this issue.

Next Steps

To resolve this issue, please revise your app to ensure that the content and controls on the screen are easy to read and interact with.

Resources

For more information, please review the following resources on the iOS Developer Center page:

- UI Do's and Don'ts

- iOS Human Interface Guidelines

- UIKit

Please make any changes you see needed to bring this app into compliance with the App Review Guidelines, then resubmit for review. Once this issue has been resolved, we can continue with the review of your app.

Best Regards,

App Store Review"

 

If your App/Game use Vuforia, then insted of updating Unity Version, Do the following that I found a working solution in vuforia thread

1. Integrate this in your project
https://developer.vuforia.com/forum...vuforia-7047-and-unity-201731f1#comment-63110
2. Replace this file
https://developer.vuforia.com/forum...vuforia-7047-and-unity-201731f1#comment-63347

 

Our app works in a very particular way. We integrated the Unity player (Unity 2017.1.1p2) inside a Native iOS App.
We fixed this issue just by commenting the whole method updateDisplayListInUnity in DisplayManager.mm

Code (CSharp):

1. - (void)updateDisplayListInUnity
2. {
3.     // [UIScreen screens] might be out of sync to what is indicated to the
4.     // application via UIScreenDidConnectNotification and UIScreenDidDisconnectNotification
5.     // notifications. For example, on disconnection [UIScreen screens] might still
6.     // have the screen that the display manager no longer knows about.
7.  
8. //    const unsigned MAX_DISPLAYS_SUPPORTED = 8; // sync this to the value on Unity side
9. //    void* screens[MAX_DISPLAYS_SUPPORTED];
10. //    unsigned screenCount = 0;
11. //
12. //    UIScreen* mainScreen = [UIScreen mainScreen];
13. //    screens[screenCount++] = (__bridge void*)mainScreen;
14. //
15. //    for (UIScreen* screen in _displayConnection)
16. //    {
17. //        if (screen == mainScreen)
18. //            continue;
19. //        screens[screenCount++] = (__bridge void*)screen;
20. //    }
21. //
22. //    UnityUpdateDisplayList(screens, screenCount);
23. }

Guess what? AirDisplay is working just fine and the app does not crash anymore during the startup.

 

Thanks, Magnetica and Yass_! (And I just saw the reply by jgvidotto - exactly!)

Updates:
I'll cover what did not work but could have helped in eventually fixing all the issues and what worked for me at least to have the app Approved.

What didn't work but could have helped:
I updated Unity 2017.1 to the patched version 2017.1.3p2 and resubmitted my App, but it was Rejected.
I attached the DelayedVuforiaInitialization script and wired it up according to the instructions in the thread linked above, but it was Rejected. The app worked fine on my phone via XCode.

The symbolicated crash report was helpful in showing at which point it crashed though.
According to the Timestamps, it crashed right after the Splash screen.

I also clarified the Instructions in the App Review field in the Submission screen in iTunesConnect so that Permissions have to be accepted and the user has to click on "Accept" / 'Continue" in my opening screens (panels).

Then what finally worked:
After receiving a screenshot instead of the symbolicated crash report, I saw that the issue was just that the Permission descriptions were not in accordance with Apple Guidelines.
So I improved the Permission descriptions, resubmitted, and received the App Approval! Fortunately, it was that simple of a fix.

What that means is that the explanation "Your app crashed on iPad or iPhone running iOS 11.2.5 connected to an IPv6 network during our review" is likely generic / broad as quoted from the reply by shoutrlabs in the Vuforia thread:

"We believe that the issue is not IPV6-related and that this error message is just plain unspecific meaning: Apple Review tested the app in an IPv6 network and it failed, but not necessarily due to IPv6.

Please forward attached symbolicated crash log by Apple to your engineers."

I also noticed that the screen did not load completely and was still transitioning when testing on my phone where the app was hanging. It could be because something stops everything from running at the point until Permissions are allowed, but I haven't looked into it further yet.

So I would suggest to check the Timestamps in the symbolicated crash report to narrow down the point when it crashed or hung. Then check for items there as they might not describe the exact problem for you.

Hope that helps!

 

Our App was rejected twice. But today we sent an appeal.

The thing is that iOS 11.2.5 has a serious bug that provokes a crash in certain devices if they use iMessage, WhatsApp, Facebook, etc. or it services. That's why they released iOS 11.2.6 with a fix.

In our case we use the Facebook SDK so we cannot guarantee it will work on iOS 11.2.5.

Let's see if the appeal works ...

EDIT: the appeal was approved and the update is now live on the AppStore.