iOS 8.0 - “failed to scene-update in time” crash

Question

I\'ve encountered the following crash while running on iOS 8.0. This is the first time I\'m seeing this so any observation will be helpful:

Incident Identifi         


        

Answer 1

Well, here's a hint. Apparently the notification message has changed from iOS 7.1 to iOS8.1

I got the same behavior/crash on my app as well and captured crash logs for each OS:

7.1 says:

Incident Identifier: 1AFAD8D6-50B3-4B5A-8EBE-2A76E4400BDA
CrashReporter Key:   8e228dccf0b7ae7d1127923c96eec86495483eae
Hardware Model:      iPhone5,3
Process:             ProcessName [2967]
Path:                /var/mobile/Applications/key/myApp.app
Identifier:          com.company.app
Version:             5.6.0042 (5.6)
Code Type:           ARM (Native)
Parent Process:      launchd [1]


Date/Time:           2014-11-04 17:32:57.089 -0800
OS Version:          iOS 7.1.1 (11D201)
Report Version:      104


Exception Type:  00000020
Exception Codes: 0x000000008badf00d
Highlighted Thread:  0


Application Specific Information:
com.company.app failed to resume in time

While iOS 8.1 says:

Incident Identifier: 960DB688-F165-4DCD-98A1-3F4AEFFB5442
CrashReporter Key:   2022d4aa4b6f69db15c58ae02734fb8172a77bba
Hardware Model:      iPhone7,2
Process:             ProcessName [175]
Path:                /private/var/mobile/Containers/Bundle/Application/key/myApp.app
Identifier:          com.company.app
Version:             5.6.0042 (5.6)
Code Type:           ARM-64 (Native)
Parent Process:      launchd [1]


Date/Time:           2014-11-04 18:05:31.933 -0800
Launch Time:         2014-11-04 17:30:28.408 -0800
OS Version:          iOS 8.1 (12B411)
Report Version:      105


Exception Type:  00000020
Exception Codes: 0x000000008badf00d
Highlighted Thread:  0


Application Specific Information:
com.company.app failed to scene-update in time

So, pretty much everything is the same except for the Application Specific Information section.

In our case there was a method running on the Main thread that wasn't completing therefore it was getting the rest of the UI stuck and the system was killing it.As soon as we fixed that the problem went away on both versions.

So check what might be causing your Main thread to hang.