Unity Issue Tracker - [iOS 11] Build crashes on remotear`::UnityUpdateDisplayList() when launching app from URL with AirPlay connected

Fixed in 2018.1.X

Fixed in 5.6.X, 2017.1.X, 2017.2.X, 2017.3.X

Votes

1

Found in

2017.2.0f3

Issue ID

960439

Regression

No

[iOS 11] Build crashes on remotear`::UnityUpdateDisplayList() when launching app from URL with AirPlay connected

iOS

Oct 18, 2017

To reproduce:
1. Open project attached by the user
2. Build it for iOS platform
3. Open build .xcodeproj file in XCode
4. Go to Product -> Scheme -> Edit Scheme
5. Select "Info" tab and tick "Wait for executable to be launched"
6. Build to device
7. Connect the device to Apple TV (to use screen mirroring)
8. After the device is connected to Apple TV go to Safari (on device) and type: airplaycrash://
9. It will ask to open an app, hit open

Expected result: Application should be launched from URL
Actual result: Application crashes on start

Reproduced with: 5.6.3p4, 2017.2.0f3, 2017.3.0b5, 2018.1.0a1
Device: iPhone 6s iOS 11.0

Not reproducible with iPad mini 3 iOS 10.3

Fixed in: 2018.1.0b1
Backported to: 2017.3.0p2, 2017.2.1p2, 2017.1.3p1, 5.6.5p3

Comments (52)

Sorcha08

Mar 22, 2018 09:29

@AGAMEMNON-PRIME and @NIKUNJ48 Can you explain better your solution?
agamemnon-prime

Mar 22, 2018 06:51

We have successfully released 2 apps by commenting out the Observers in the init section. I have added the "replace" to our xcode postprocessing so that we can build with cloud build. We used 5.6.5f1.
Nikunj48

Mar 22, 2018 05:21

Hi BRIGHTONRICH,

I have submitted app to appstore and got rejected,
I have tested it with Reflector 3 to reproduce airplay issue
Game is crashed without make comment in Displaymanager.mm file,
After commenting those code in "init" method game is working with device.

Rejection message from Apple

Guideline 2.1 - Performance

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

We have attached detailed crash logs to help troubleshoot this issue.

Detailed Crash log : https://drive.google.com/open?id=1RAzFgUA94GccczAng6xdsftEli40fT9N

Resources used,
Unity 5.6.4f1
xCode Version 9.2 (9C40b)
iOS version 11.2.6 (iPhone 6s)
Use Reflector 3 for Airplay support in MAC
brightonrich

Mar 21, 2018 15:05

@PL_AYGROUND What version is that stack trace from?
brightonrich

Mar 21, 2018 14:03

@ADAMLIU Could you post the log from your rejection please?
cpth15

Mar 20, 2018 19:04

Same here. Submitted with Unity 5.6.5p3 and got rejected with "Termination Reason: Namespace SPRINGBOARD, Code 0x8badf00d".
Sporkula

Mar 20, 2018 18:23

I still get the springboard fail on a build using Unity 5.6.5p3.
AdamLiu

Mar 20, 2018 14:50

Submitted with Unity 2017.3.1p4, got rejected because of "Your app crashed on iPad or iPhone running iOS 11.2.5 connected to an IPv6 network during our review." Anyone knows which version can pass the review?
agamemnon-prime

Mar 20, 2018 07:08

Our app got rejected when built with Unity 5.6.5p3.

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.worldofwaw.test 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): 26.160 (user 26.160, system 0.000), 84% CPU", | "Elapsed application CPU time (seconds): 13.330, 43% CPU" | )
Triggered by Thread: 0
samzgamz

Mar 19, 2018 15:44

My App also got rejected by Apple today. Using Unity 2017.3.1p1. The Crash report that I have received from Apple is attached : https://drive.google.com/open?id=1Q4kNx_rCUK-gD8GvdM7HRv7F3ogiyFQC

I have no idea what the problem is. The app works absolutely fine when tested on real devices. I am assuming that my case is also related to this bug. A small snippet of the error shows a problem with NSMapTable. I could see that the DisplayManager.mm uses it so maybe the error could lie there. Hope this helps.

Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Triggered by Thread: 7

Application Specific Information:
*** Terminating app due to uncaught exception 'NSGenericException', reason: '*** Collection <NSConcreteMapTable: 0x1073423e0> was mutated while being enumerated.'
terminating with uncaught exception of type NSException
abort() called