iOS App rejected due to IPv6 error

hi all,
our App is jest been rejected.

Your app crashed on iPad or iPhone running iOS 11.2.5 connected to an IPv6 network during our review.

the crash log shows this error:

Filtered syslog:
Timestamp Thread Type Activity PID
2018-03-03 01:33:27.3849 -0800 0x17023 1024 0x0 6302 libsystem_network.dylib: -[NWConcrete_nw_connection initWithEndpointarameters:] @ endpoint: [perf-events.cloud.unity3d.com:443] parameters: [stream, pid: 6302, sanitized url: https://perf-events.cloud.unity3d.com/symbolicate, tls]
2018-03-03 01:33:27.3917 -0800 0x17023 1024 0x0 6302 libsystem_network.dylib: nw_endpoint_handler_start [1 perf-events.cloud.unity3d.com:443 initial path (null)]
2018-03-03 01:33:27.4150 -0800 0x17023 1024 0x0 6302 libsystem_network.dylib: nw_connection_endpoint_report [1 perf-events.cloud.unity3d.com:443 initial path (null)] reported event path:start
2018-03-03 01:33:27.4159 -0800 0x17023 1024 0x0 6302 libsystem_network.dylib: nw_connection_endpoint_report [1 perf-events.cloud.unity3d.com:443 waiting path (satisfied)] reported event path:satisfied
2018-03-03 01:33:27.4229 -0800 0x1700a 1024 0x0 6302 AssertionServices: BKSWorkspace created.
2018-03-03 01:33:27.4429 -0800 0x17023 1024 0x0 6302 libsystem_network.dylib: nw_connection_endpoint_report [1 perf-events.cloud.unity3d.com:443 waiting path (satisfied)] skipping state update
2018-03-03 01:33:27.4477 -0800 0x17023 1024 0x0 6302 libsystem_network.dylib: nw_connection_endpoint_report [1 perf-events.cloud.unity3d.com:443 in_progress resolver (satisfied)] reported event resolver:start_dns
2018-03-03 01:33:27.4510 -0800 0x17023 1024 0x0 6302 libsystem_network.dylib: nw_resolver_create_dns_service_locked Starting host resolution perf-events.cloud.unity3d.com:443, flags 0x4000d000 proto 0
2018-03-03 01:33:27.4527 -0800 0x1703a 1024 0x0 6302 libsystem_network.dylib: nw_resolver_host_resolve_callback flags=0x3 ifindex=0 error=NoSuchRecord(-65554) hostname=perf-events.cloud.unity3d.com. addr=::.0 ttl=60

this domain doesn't have an IPv6 AAAA record!?

http://ready.chair6.net/?url=perf-events.cloud.unity3d.com

any idea?
it's enough to disable performance report in production build to solve this?

thanks

Emiliano

 

Same exact issue here :c It is quite frustrating.
Did you manage to find a workaround?

 

unfortunately, no.
I tried to disable all performance and analytics services.
rejected again and again.

but now the error is different:

Created client agent: <UIApplicationSceneClientAgent: 0x1c4004440>
2018-03-04 08:28:24.1996 -0800 0xb2e9 1024 0x0 4578 UIKit: View did appear: <SplashScreenController: 0x11bd59fc0> 1
2018-03-04 08:28:24.2010 -0800 0xb2e9 1024 0x0 4578 UIAccessibility: Did post notification. notification: (1001) error:0 datanull)
2018-03-04 08:28:24.2089 -0800 0xb2e9 1024 0x0 4578 UIAccessibility: Did post notification. notification: (4002) error:0 data:{
controllerClass = SplashScreenController;
event = ViewDidAppear;
}

IPv6 and splash screen controller..???!!???

unity guys: can you help us?

I tried to follow Apple instructions to create an IPv6 netwoek through a sharing connaction and everything work.
we tested the App using an external service and they did a lot of test using aboun 150 different iOS devices, without errors.

we can't develop games for 15 months and be stopped by Apple 20 day before official launch!

so sad..

 

We just got the same rejection message

 

You need to symbolicate the provided crash report to identify where the crash occurred.

 

My old app was approved, then I changed the icon, uploaded again...Rejected due the same error of the topic

 

HI!
I found the problem, and the solution.

Apple is reviewing my App using a device attached to an AppleTV and sharing the screen via AirPlay.
the App has been compiled using unity 2017.2.1p1 and it has a bug, patched in the very next version.

https://issuetracker.unity3d.com/issues/ios-11-build-crashes-on-remotear-unityupdatedisplaylist-when-launching-app-from-url-with-airplay-connected


so the real error isn't a network error but simply the App can't start in theit testing Environment (ipv6).

hope this information could help someone else.

thanks

E.

 

Thanks for the info!
Is the new version already out?

 

no, waiting foor review.
fingers tossed!!

..but I was able to reproduce the problem and solve it with the latest unity version, so I need only a bit of fortune

 

I also get rejection with a same reason.

Your app crashed on iPad or iPhone running iOS 11.2.5 connected to an IPv6 network during our review.

App was compiled using Unity 2017.3.1p3. @magnetica what unity version did you used?

 

I used the following versions:
Unity 2017.30f3
Unity 2017.30p4
Unity 2017.3.1
Unity 2017.2.0.f3
And every time my app rejected - "Guideline 2.1 - Performance Your app crashed on iPad or iPhone running iOS 11.2.5 connected to an IPv6 network during our review."
Already tried to write an appeal (on the advice https://stackoverflow.com/questions...-app-review-team-crash-unity-app-with-vuforia), but it unfortunately did not help. If someone managed to overcome this error please write how you did it.

 

I've exactly the same rejection, someone found a workaround ?

 

hi,
the rejected App had been compiled using Unity 2017.2.1p1.
the approved version using 2017.3.1p3

 

hi,
try to analyze the symbolicated crash log, or (simpler) try your App using an AirPlay connection.
you can use an Apple TV or an emulator (I used Reflecter 3 for Mac. 7 days trial).
connect your device and share the screen, then start your App.
it it crashes immediately, try to compile the App with another version.

follow this link

https://issuetracker.unity3d.com/is...launching-app-from-url-with-airplay-connected

it talks about the Unity bug and gives you the patched versions.

hope it helps

 

Okay, I just tried TestFlight version of the build with Reflecter 3 (same build which failed review) and game not crash, it working just perfectly fine.

 

ok, the Apple reviewer isn't testing your App using AirPlay and the crash should be elsewhere.
you could use a proxy to fetch all network traffic and look for not IPv6 calls/domains.

are you using some External services?

 

Same problem here
Everything works fine in test environment
Unity 2017.2.0.f3 (notice that there's a bug in 2017.3 that prevents us from updating for now)
This is really frustrating : \

 

We were having the same issue and, like magnetica, were having the same rejection problems due to screen-streaming being used in the testing environment.

https://issuetracker.unity3d.com/is...launching-app-from-url-with-airplay-connected

The fix is present in 2018.1.0b1, but has also been back-ported to patched Unity builds that should all contain the fix:

2017.3.0p2
2017.2.1p2
2017.1.3p1

After updating our build of unity from 2017.2.1 to 2017.2.1p2, our app was immediately approved.

 

GREAT!!
Very glad to hear our experience helped some other user.

 

Does this crash occurs in all latest iOS versions or only 11.2.5? Because my previous game was built with 2017.3.1p1 and go through the review. Is it possible that reviewers not always testing with this iOS version?

 

I also had my app approved on previous iOS versions and all of the logs for my rejected apps were from devices running 11.2.5. It seems possible to me that the bug is either isolated to this iOS version or starting with this version. I have not tested 11.2.6 and any attempt to ask apple to test with their most up-to-date iOS version was met with radio silence.

Maybe your tester was using 11.2.6 or they were not streaming their screen with AirPlay.

 

yes, I agree.
the problem about AirPlay occurs starting from iOS 11.2.5

 

Tuning in here and currently on 2017.1.1f1. I'm glad I found this thread as I had the same issue where my previous build was accepted, but now I am encountering the same issue in the Resolution Center. My app runs just fine on my iPhone updated to 11.2.6 as installed from XCode directly.

I will update Unity to 2017.3.1p3, build, submit, and report back here.

 

Thanks for the advice, but the rejection has just come from the Unity 2017.2.1.p2 where the bug with AirPlay should be patched. It looks like it's something else...

 

Same issue here. Going to try the just released Patch 2017.3.1p4 and will get back here with the update

 

Bad news, guys..
Yesterday I uploaded a new build to solve a little bug and add some extra image marker (it’s a vuforia based app) and today Apple rejected this build.
It has been made with the same unity version.
This time the crash log is different and it shows an error related to a timeout.
It takes too much time to go foreground.
I found a recent thread on vuforia forum, tali kg about unity 2017.3.1p3, vuforia and this error code.

... neverending story...

I’ll keep you updated

 

so if I understand this correctly, your most recent rejection was due to vuforia and not related to the original ipv6 error as outlined in your original post, correct?

 

will the fix backport to unity 4.7?

 

Yes, the crash log analysis shows some errors during vuforia initialization but Apple rejected the app giving the same fake information: the app must work in ipv6 only network.

The funny thing is that a lot of people receive the same message form Apple but the real problem is something else.. so Apple should explain how to reproduce their testing environment instead of reject Apps with wrong errors!

 

According to the issue tracker, they are working on patching back to 5.6. Keep an eye out on the road map and for the latest patch release.

 

I asked for more information about the crash from reviewer and the game passed the review. However, they did not answered my questions. Would be better get the real solution for this problem.

 

2017.3.1p4 did the trick

 

My game was rejected with 2017.3.1p4
Bug:
Your app crashed on iPad or iPhone running iOS 11.2.5 connected to an IPv6 network during our review.

Exception Type: EXC_CRASH (SIGKILL)

Exception Codes: 0x0000000000000000, 0x0000000000000000

Exception Note: EXC_CORPSE_NOTIFY

Termination Reason: Namespace SPRINGBOARD, Code 0x8badf00d

Termination Description: SPRINGBOARD, scene-create watchdog transgression: com.appzek.WhySo exhausted real (wall clock) time allowance of 10.00 seconds | | ProcessVisibility: Foreground | ProcessState: Running | WatchdogEvent: scene-create | WatchdogVisibility: Foreground | WatchdogCPUStatistics: ( | "Elapsed total CPU time (seconds): 32.230 (user 32.230, system 0.000), 98% CPU", | "Elapsed application CPU time (seconds): 1.988, 6% CPU" | )

Triggered by Thread: 0

 

2017.3.1p3 did approved too, finally

 

Hi,
Our app had been rejected firstly because Apple was using a device connected via AirPlay.
The bug has already patched in some unity versions.

The second reason was a problem about camera permissions/initialization.
The App uses Vuforia so they made a patch and the App passed the approval process.

If your Apps use some sdk that access camera (for AR or take photos), the cause could be those sdk.

Look at this thread about vuforia problem.

https://developer.vuforia.com/forum...vuforia-7047-and-unity-201731f1#comment-63092

Hope it helps.

 

Today, My game was approved after I sent a message to apple. I didn't upload any new build. So Unity version 2017.3.1p4 is OK. I wrote to apple that I tested on simulator iPhone X 11.2 without crashing.
Hope that helps.

 

hi,
our first App has been approved after installing a patch provided by Vuforia.
the second one.. no!
the reason given by Apple is the same: IPv6 bla bla.. but the crash log reports the SPRINGBOARD error.

I think unity + Vuforia should contact Apple and try to solve this problem.
they could have the "power" to contact someone and find a final solution.

thanks

 

Hey magnetica, we're having the same issue and would love to try this patch. Is the patch available online or did you have to directly contact Vuforia?

Thanks!

 

hi,
they sent us the patch directly.

you should contact the support team.

we opened a ticked using out VIP program.

 

Just sent them a DM for the patch, fingers crossed for a quick response. Our deadline is looming tomorrow... We will try to include the link to the megathread on Vuforia's website with our submission too, hopefully Apple might approved based on that thread.

Thanks so much for your help!

 

awesome!

10 minuts ago Apple started to review again our App.
we mentioned the Vuforia thread too. hope it works.... because the patch is not really working.
they approved another App after patching, but the second one had been rejected.

so frustrating..

 

update: our second App has been approved!

we added an answer in the resolution center linking Vuforia thread.

they reviewed the App and approved it.



we are safe.. until next release

 

Got rejected using 2017.3.1p4 too, exact the same error from Apple Review Team.
I also sent a message to Apple (replied in resolution center and sent an appeal), hope the app can be approved this time (no new binary submitted). I'll post update here once I got a reply. Finger crossed.

 

Update: The appeal is also rejected. However there can still be more replies from the resolution center. Gonna wait till tomorrow morning.

 

More Update: My game is now ready for sale.

 

I just got rejected with the same reason. Using 5.6.4f1.

Downloading the patched version 5.6.5 right now.. Anyone using the patched version and successfully have had their app approved? Or is it something else not related to Unity Editor?

 

Here is an update from Vuforia Support regarding this issue in the Forums. Hope it works! I'll update as well..

https://developer.vuforia.com/forum...vuforia-7047-and-unity-201731f1#comment-63110

where you'll find this from the post on March 28, 2018: DelayedVuforiaInitialization.zip 2.25 KB

 

Hi Magnetica, do you have the link or can you copy the resolution here?

Thanks

 

Hi,
This is the vuforia thread.

https://developer.vuforia.com/forum...vuforia-7047-and-unity-201731f1#comment-63134

Hope It helps

 

Hi all,
I had same issue with Unity 5.6.4.f1 for several times. I just update Xcode yesterday with new version 9.3(9E145) and submitted a new binary of my app. Miracles! It passed! No more IPv6 error message. Hope works for you also.