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)

gregb

Jun 29, 2018 18:11

Hello Unity Team,

there is a fix or patch for Unity 2017.4.3.f1?

We can't submit with no it.
korober

May 01, 2018 12:22

passed app store review with 2017.3.0p2
korober

Apr 19, 2018 06:33

Does Unity 2017.4.1f1 has the issue or it has been fixed by backporting?
sarebots2

Apr 10, 2018 13:35

I got the same error on Unity 2017.3.1f1 and my app got rejected on the App Store.
I see the fix was backported to: 2017.3.0p2, 2017.2.1p2, 2017.1.3p1, 5.6.5p3

Since it didn't make sense for me to downgrade, I upgraded my Unity to the latest stable version, ie, 2018.4.1f1 LTS.

Before I submit again, it will be helpful to know if the fix has been backported to 2018.4.1f1 LTS version.
a909413016

Apr 04, 2018 07:37

@AGAMEMNON-PRIME
Have you solve the "exhausted real (wall clock) time allowance of 10.00 seconds" problem?
which still crash after remove the observers.
platforms

Mar 31, 2018 16:09

We are facing the same issue with Unity 2017.3.1p1. Is there backport for 2017.3.1 version for this bug?

We should release a new version of our app, but can't get through Apple app review because of this bug..
meedabit

Mar 28, 2018 20:53

Thanks @ADRIANCLARK for posting a workaround to the app store submission failures for those using Vuforia.

Vuforia has released a similar version of the workaround. That script and patch updates can be found here: https://developer.vuforia.com/forum/ios/workaround-ios-apps-failing-review
AdrianClark

Mar 27, 2018 19:31

@BRIGHTONRICH and Others

For anyone who is using Vuforia, there is a second bug which is causing apps to fail review in addition to the Airplay bug mentioned in this issue. Unfortunately both bugs are a result of changes in Apple's iOS review test environment, which is why they have shown up at the same time. The description of the fault (devices with IPv6) is also a red herring, and is not related to the problems themselves.

I can see a few people are having this Vuforia issue in this thread (based on their stack traces showing the last symbolicated call stack line showing Vuforia.Init). I reported this issue a few weeks ago to Vuforia, the thread is here:

https://developer.vuforia.com/forum/ios/ios-apps-failing-app-review-vuforia-7047-and-unity-201731f1

The Vuforia support team were able to tell me what the Vuforia library was trying to do at that specific point based on the stack trace, and I have written a work around which resolves this bug and posted it in the Vuforia thread here:

https://developer.vuforia.com/forum/ios/ios-apps-failing-app-review-vuforia-7047-and-unity-201731f1#comment-63110

This second bug is caused by Vuforia halting the main thread while it waits for the user to accept or deny the camera permission (this has since been confirmed by Apple as the problem). The new iOS testing environment sees this pause as the app freezing, and after 10 seconds kills the app (hence the "com.companyname.appname exhausted real (wall clock) time allowance of 10.00 seconds). The work around effectively disables Vuforia's camera permission code, and instead requests camera permission in the correct callback driven fashion, only starting Vuforia once the user has accepted or denied permission.

The Vuforia support team is currently working on an official fix, but for the moment their official response for people who can't wait is to use the work around that I have provided in that thread.

I have used the work around for multiple updates to several apps and they have passed review with no issue.

Hope this is helpful.

Cheers,
Adrian
agamemnon-prime

Mar 27, 2018 17:33

@BRIGHTONRICH, it was built with 5.6.5f1. The previous build also, but that one was approved.
beaADS

Mar 27, 2018 09:06

If it's of any help. My app was finally accepted after 5 days waiting for the review. Previously it was rejected with different unity versions including some patches. This last one version I have:
- Unity 2017.3.1p4
- Vuforia (last version integrated)
- Facebook SDK
- Screen record for pictures
I also included the @NIKUNJ48's fix (remove the observers)

I don't know if it was luck or because of the fix

I don't know if apple approved this one of that fix or for any other reason.