Crashes when you force close an iOS app with another view controller up?

We have an issue where if you force close the app while an Ad is up, the app crashes.
Using AdMob and it happens with any of the mediated Ads.

It generates tens of thousands of crashes for us in our logs (a player wouldn't notice that it's crashing though).
I can't anyone mentioning this when I google the issue! Is it just me? I am going crazy here.

AdMob have investigated and said its a unity issue, and happens even if you bring up a blank view controller.

I have submitted a bug, But it would be great to know if anyone else is experiencing this. Basically just show an Ad and then force quit the game.

Other details:
Only happens on iOS 13 devices.
Only started when we upgraded to 2019.3

Crashes look like this:

0 UnityFramework 0x10317fd14 UnityIsOrientationEnabled + 250 (ScreenManager.h:250)
1 UnityFramework 0x10317fd14 UnityIsOrientationEnabled + 250 (ScreenManager.h:250)
2 UnityFramework 0x10241859c EnabledAutorotationInterfaceOrientations() + 178 (UnityViewControllerBase+iOS.mm:178)
3 UnityFramework 0x10240d05c -[UnityAppController application:supportedInterfaceOrientationsForWindow:] + 201 (UnityAppController.mm:201)
4 UIKitCore 0x1b199c140 -[UIApplication _supportedInterfaceOrientationsForWindow:] + 108
5 UIKitCore 0x1b1397a64 -[UIViewController __supportedInterfaceOrientations] + 256
6 UIKitCore 0x1b1389028 -[UIViewController _preferredInterfaceOrientationGivenStatusBarAndDeviceAndOrientation:] + 104
7 UIKitCore 0x1b1397680 -[UIViewController _preferredInterfaceOrientationForPresentationInWindow:fromInterfaceOrientation:] + 544
8 UIKitCore 0x1b12a81c8 -[_UIFullscreenPresentationController _adjustOrientationIfNecessaryInWindow:forViewControllerreservingViewController:] + 576
9 UIKitCore 0x1b129deb8 -[UIPresentationController _dismissWithAnimationController:interactionController:target:didEndSelector:] + 684
10 UIKitCore 0x1b139201c __99-[UIViewController _dismissViewControllerWithAnimationController:interactionController:completion:]_block_invoke_2 + 72
11 UIKitCore 0x1b1e20c14 +[UIView(Animation) performWithoutAnimation:] + 96
12 UIKitCore 0x1b1391e98 -[UIViewController _dismissViewControllerWithAnimationController:interactionController:completion:] + 580
13 UIKitCore 0x1b1e20c14 +[UIView(Animation) performWithoutAnimation:] + 96
14 UIKitCore 0x1b1391b4c -[UIViewController _dismissViewControllerWithTransition:from:completion:] + 816
15 UIKitCore 0x1b1391228 -[UIViewController dismissViewControllerWithTransition:completion:] + 1200
16 UIKitCore 0x1b1390c90 -[UIViewController _performCoordinatedPresentOrDismiss:animated:] + 508
17 UIKitCore 0x1b13933a0 -[UIViewController dismissViewControllerAnimated:completion:] + 132
18 UIKitCore 0x1b19d028c __68-[UIWindow _removeAllViewControllersFromWindowHierarchyFromDealloc:]_block_invoke + 60
19 UIKitCore 0x1b138b154 +[UIViewController _performWithoutDeferringTransitionsAllowingAnimation:actions:] + 168
20 UIKitCore 0x1b19cff1c -[UIWindow _removeAllViewControllersFromWindowHierarchyFromDealloc:] + 288
21 UIKitCore 0x1b19d0438 -[UIWindow setRootViewController:] + 284
22 UnityFramework 0x10240cf40 UnityCleanupTrampoline + 168 (UnityAppController.mm:168)
23 UnityFramework 0x10240df04 -[UnityAppController applicationWillTerminate:] + 468 (UnityAppController.mm:468)
24 UIKitCore 0x1b199dae0 -[UIApplication _terminateWithStatus:] + 244


Also like this, looks like the same thing:

Crashed: com.apple.main-thread
0 UnityFramework 0x1050a840c MetalHeap::AliasResources() + 89324
1 UnityFramework 0x1050a840c MetalHeap::AliasResources() + 89324
2 UnityFramework 0x10433539c UnityAdsEngineSetDidFinishCallback + 30808
3 UnityFramework 0x104329e5c (Missing)
4 UIKitCore 0x19c905180 -[UIApplication _supportedInterfaceOrientationsForWindow:] + 112
5 UIKitCore 0x19c2d739c -[UIViewController __supportedInterfaceOrientations] + 260
6 UIKitCore 0x19c2c8278 -[UIViewController _preferredInterfaceOrientationGivenStatusBarAndDeviceAndOrientation:] + 108
7 UIKitCore 0x19c2d6f90 -[UIViewController _preferredInterfaceOrientationForPresentationInWindow:fromInterfaceOrientation:] + 548
8 UIKitCore 0x19c1e1b78 -[_UIFullscreenPresentationController _adjustOrientationIfNecessaryInWindow:forViewControllerreservingViewController:] + 604
9 UIKitCore 0x19c1d75ac -[UIPresentationController _dismissWithAnimationController:interactionController:target:didEndSelector:] + 652
10 UIKitCore 0x19c2d16a4 __99-[UIViewController _dismissViewControllerWithAnimationController:interactionController:completion:]_block_invoke_2 + 76
11 UIKitCore 0x19cda6d54 +[UIView(Animation) performWithoutAnimation:] + 104
12 UIKitCore 0x19c2d14f8 -[UIViewController _dismissViewControllerWithAnimationController:interactionController:completion:] + 608
13 UIKitCore 0x19cda6d54 +[UIView(Animation) performWithoutAnimation:] + 104
14 UIKitCore 0x19c2d118c -[UIViewController _dismissViewControllerWithTransition:from:completion:] + 832
15 UIKitCore 0x19c2d084c -[UIViewController dismissViewControllerWithTransition:completion:] + 1236
16 UIKitCore 0x19c2d0270 -[UIViewController _performCoordinatedPresentOrDismiss:animated:] + 528
17 UIKitCore 0x19c2d2af0 -[UIViewController dismissViewControllerAnimated:completion:] + 148
18 UIKitCore 0x19c93a9f8 __68-[UIWindow _removeAllViewControllersFromWindowHierarchyFromDealloc:]_block_invoke + 64
19 UIKitCore 0x19c2ca500 +[UIViewController _performWithoutDeferringTransitionsAllowingAnimation:actions:] + 176
20 UIKitCore 0x19c93a678 -[UIWindow _removeAllViewControllersFromWindowHierarchyFromDealloc:] + 304
21 UIKitCore 0x19c93abb4 -[UIWindow setRootViewController:] + 288
22 UnityFramework 0x104329d40 (Missing)
23 UnityFramework 0x10432ad04 (Missing)
24 UIKitCore 0x19c906bc0 -[UIApplication _terminateWithStatus:] + 248

 

I confirm that, we have a exactly same issue, I fixed it in one app by downgrading Unity version to 2019.2. Other proposed fix is in this post but I do not know if that is a good solution

 

Cause of error is on line 5. in example code
[_UnityAppController window].rootViewController = nil;
(in UnityAppController.mm file).

Commenting it prevent error from happening.

Code (CSharp):

1. extern "C" void UnityCleanupTrampoline()
2. {
3.     // Unity view and viewController will not necessary be destroyed right after this function execution.
4.     // We need to ensure that these objects will not receive any callbacks from system during that time.
5.     //[_UnityAppController window].rootViewController = nil;
6.     [[_UnityAppController unityView] removeFromSuperview];
7.  
8.     // Prevent multiple cleanups
9.     if (_UnityAppController == nil)
10.         return;
11.  
12.     [KeyboardDelegate Destroy];
13.  
14.     SensorsCleanup();
15.  
16.     Profiler_UninitProfiler();
17.  
18.     [DisplayManager Destroy];
19.  
20.     UnityDestroyDisplayLink();
21.  
22.     _UnityAppController = nil;
23. }

 

Thanks heaps for the reply, I really appreciate it!
Was really struggling to find any trace of this issue, so it's good to know it's not just me!

I will investigate those links, they look like they could be helpful.

 

From my own experience, had the same issues with many native crashes after upgrading to 2019.3.1f9,.. but after downgrading back to 2019.3.1f6 all is fine again.

 

In my case, I had also to comment out this line

[KeyboardDelegate Destroy];

It was causing a crash because a keyboard selector was nil

 

i facing the issue . i tried all the above possibilities but still facing the same .

 

We're are seeing the same errors in our Crashes and Exceptions but players aren't reporting any issues.

Did anyone find a solution? It's been a month since the last post here and I don't see anything in the release notes to suggest Unity has fixed it?

 

I had the same, it was caused by a n objectiveC plugin that instantiated a UIViewController at start and stored it in a global variable

 

@Alexey If it's fixed in 2020.1/2020.2 has it or can it be backported to 2019.4?

 

@Alexey bump

Adding the fix to alpha/beta versions of Unity is not very helpful since this bug is likely not a big concern to developers without published games/apps.

 

We have the same issues several reports of crashes - but its always just on closing, so yeah it is not causing issues for customers, but it makes it bad for tracking crashes... and I think it should not crash on closing either...

I also agree on PAndaArcada - fixing it for alpha/beta version is nice but the main focus for this fix should be the LTS version.

 

@Alexey

 

Is this the fix? Recently released in 2019.4.4f1
https://issuetracker.unity3d.com/is...few-frames-when-the-splash-screen-is-disabled

 

It's still happening on 2019.4.6f1 :'(

 

Your call-stack has nothing related with the issue & call-stack described here. Please thoroughly verify what you claim.

 

It's a VERY similar stack trace than in the the opening post:

Just as the opening post the crash happens through UnityAdsEngineSetDidFinishCallback, when the app is closed/backgrounded while an ad.

 

Hi, we have encountered the same issue in Unity LTS Version 2019.4.8f1. We went LIVE the game last week in App Store and get massive number of Crashes. We are using Firebase Crashlytics. Among 3.3K unique users 8.8K crashes have been happened. Our user base is huge and we don't want let our Ratings&Reviews down. Please have a quick look.



EXC_BAD_ACCESS KERN_INVALID_ADDRESS 0x000000000000024a
MetalHeap::AliasResources()

Crashed: com.apple.main-thread
0 UnityFramework 0x101cf5090 MetalHeap::AliasResources() + 151952
1 UnityFramework 0x100ae2b00 UnityAdsEngineSetDidFinishCallback + 29816
2 UIKitCore 0x1afe02228 <redacted> + 168
3 UIKitCore 0x1afe17f78 <redacted> + 572
4 UIKitCore 0x1b0477ac0 <redacted> + 360
5 UIKitCore 0x1b0477814 <redacted> + 852
6 UIKitCore 0x1b0483b5c <redacted> + 248
7 UIKitCore 0x1b04799c8 <redacted> + 388
8 UIKitCore 0x1afe33f68 <redacted> + 172
9 UIKitCore 0x1b08e46f4 <redacted> + 204
10 UIKitCore 0x1afe33d5c <redacted> + 164
11 UIKitCore 0x1afe33c34 <redacted> + 492
12 UIKitCore 0x1b0477118 <redacted> + 580
13 UIKitCore 0x1b04796f4 <redacted> + 1420
14 UIKitCore 0x1b0479c08 <redacted> + 408
15 UIKitCore 0x1b0478fdc <redacted> + 128
16 UIKitCore 0x1afd200b0 <redacted> + 504
17 UIKitCore 0x1afd1fdf4 <redacted> + 880
18 UIKitCore 0x1afd15aac <redacted> + 684
19 UIKitCore 0x1afe090fc <redacted> + 72
20 UIKitCore 0x1b08df16c <redacted> + 96
21 UIKitCore 0x1afe08f78 <redacted> + 580
22 UIKitCore 0x1b08df16c <redacted> + 96
23 UIKitCore 0x1afe08c2c <redacted> + 816
24 UIKitCore 0x1afe08304 <redacted> + 1200
25 UIKitCore 0x1afe07d6c <redacted> + 508
26 UIKitCore 0x1afe0a474 <redacted> + 132
27 UIKitCore 0x1b0470b50 <redacted> + 60
28 UIKitCore 0x1afe02228 <redacted> + 168
29 UIKitCore 0x1b04707f0 <redacted> + 284
30 UIKitCore 0x1b0470cfc <redacted> + 284
31 UnityFramework 0x100ad791c (Missing)
32 UnityFramework 0x100ad89c0 (Missing)
33 UIKitCore 0x1b043d9a4 <redacted> + 244
34 UIKitCore 0x1afbdb0d0 <redacted> + 124
35 UIKitCore 0x1afbdad58 <redacted> + 216
36 UIKitCore 0x1b0433b44 <redacted> + 212
37 FrontBoardServices 0x1b15048a0 <redacted> + 84
38 FrontBoardServices 0x1b152f9bc <redacted> + 76
39 FrontBoardServices 0x1b1515bfc <redacted> + 232
40 FrontBoardServices 0x1b152f94c <redacted> + 124
41 libdispatch.dylib 0x1ac04a524 <redacted> + 16
42 libdispatch.dylib 0x1abff3434 <redacted> + 224
43 FrontBoardServices 0x1b1554850 <redacted> + 40
44 FrontBoardServices 0x1b155451c <redacted> + 404
45 FrontBoardServices 0x1b1554a44 <redacted> + 28
46 CoreFoundation 0x1ac302ad8 <redacted> + 24
47 CoreFoundation 0x1ac302a30 <redacted> + 80
48 CoreFoundation 0x1ac3021b8 <redacted> + 184
49 CoreFoundation 0x1ac2fd1e8 <redacted> + 788
50 CoreFoundation 0x1ac2fcba8 CFRunLoopRunSpecific + 424
51 GraphicsServices 0x1b6473344 GSEventRunModal + 160
52 UIKitCore 0x1b04383e4 UIApplicationMain + 1932
53 UnityFramework 0x100adcd70 UnityAdsEngineSetDidFinishCallback + 5864
54 wcc3 0x10080fe1c main + 28 (main.mm:28)
55 libdyld.dylib 0x1ac1848f0 <redacted> + 4

 

Do anyone have found the solution?

 

Still have crashes after a few seconds of exiting the game as well on iOS. Looking into it...

 

@Alexey ...did you find out what was happening on this front?

 

How did you get that log report ? is some kind of asset?
Thanks in advance

 

Can we get more information on which Unity versions have the supposed fix?

 

I'm getting this issue on Unity 2019.4.2f1, we are currently trying fixes advised by arkenthera and zoranigic. Our logs come from firebase crashlytics. Has anyone confirmed if these are related to UnityAds? or is it just Unity?

 

Not sure if this will help in any way, but we have the same crashes without using Unity Ads nor Firebase / Crashlytics nor Unity IAP or any other Unity services. It seems like a core engine issue (at least for us).

EDIT: And it is still present in 2020.1.6f1

Cheers,
Charles

 

The crash stopped happening after upgrading to Unity 2019.4.16 @dean0

 

Thanks for the update Tareq. Anyone else fixed this issue by upgrading to Unity 2019.4.16+?

 

I had that issue on 2019.3, and still got on 2020.1, but as I understood it had to be fixed. In my case this happened when user force close the game while interstitial AdMob add was playing.
The fix here helped - just comment 1 line of code in XCode

 

I am using the version 2020.1.17f and I have the same issue, any hit to how to solve this?

 

I tried your fix, it work well when builded on device, but if I publish the version to the store the problem still occurs, how did you solved?

 

Hi

Anybody found any fix for this issue?

UnityFramework: -[UnityAppController pickStartupWindowScene:] + 492

We are getting lot of crashes in xcode after iOS 15.

 

@Alexey I'm having a very similar exception, in my case it happens when a push notification from CloudKit is sent to my device and its on background.
Is it the same problem?
Right now im on 2020.3.30, should be fixed in latest one ? (2020.3.31) ?

[SIZE=4]Exception Note:  EXC_CORPSE_NOTIFY

Triggered by Thread:  0



Last Exception Backtrace:

0   CoreFoundation                   0x18bcf7708 __exceptionPreprocess + 220 (NSException.m:199)

1   libobjc.A.dylib                   0x1a08017a8 objc_exception_throw + 60 (objc-exception.mm:565)

2   CoreFoundation                   0x18bbf93b8 +[NSException raise:format:arguments:] + 100 (NSException.m:146)

3   Foundation                       0x18cfcf4c4 -[NSAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 132 (NSException.m:231)

4   UnityFramework                   0x1008faa10 -[UnityAppController pickStartupWindowScene:] + 492 (UnityAppController.mm:328)

5   UnityFramework                   0x1008fac58 -[UnityAppController application:didFinishLaunchingWithOptions:] + 400 (UnityAppController.mm:353)

6   UnityFramework                   0x100d2af34 -[ISN_UIApplicationDelegate application:didFinishLaunchingWithOptions:] + 140 (ISN_UIApplicationDelegate.mm:71)

7   UIKitCore                         0x18e6e4980 -[UIApplication _handleDelegateCallbacksWithOptions:isSuspended:restoreState:] + 360 (UIApplication.m:2279)

8   UIKitCore                         0x18e6e6414 -[UIApplication _callInitializationDelegatesWithActions:forCanvas:payload:fromOriginatingProcess:] + 3504 (UIApplication.m:2671)

9   UIKitCore                         0x18e6ec560 -[UIApplication _runWithMainScene:transitionContext:completion:] + 1244 (UIApplication.m:4201)

10  UIKitCore                         0x18dd401a4 -[_UISceneLifecycleMultiplexer completeApplicationLaunchWithFBSScene:transitionContext:] + 152 (_UISceneLifecycleMultiplexer.m:436)

11  UIKitCore                         0x18e2a9458 _UIScenePerformActionsWithLifecycleActionMask + 104 (_UISceneLifecycleState.m:109)

12  UIKitCore                         0x18dd40d3c __101-[_UISceneLifecycleMultiplexer _evalTransitionToSettings:fromSettings:forceExit:withTransitionStore:]_block_invoke + 224 (_UISceneLifecycleMultiplexer.m:549)

13  UIKitCore                         0x18dd407fc -[_UISceneLifecycleMultiplexer _performBlock:withApplicationOfDeactivationReasons:fromReasons:] + 484 (_UISceneLifecycleMultiplexer.m:501)

14  UIKitCore                         0x18dd40b4c -[_UISceneLifecycleMultiplexer _evalTransitionToSettings:fromSettings:forceExit:withTransitionStore:] + 768 (_UISceneLifecycleMultiplexer.m:548)

15  UIKitCore                         0x18dd40388 -[_UISceneLifecycleMultiplexer uiScene:transitionedFromState:withTransitionContext:] + 340 (_UISceneLifecycleMultiplexer.m:454)

16  UIKitCore                         0x18dd488cc __186-[_UIWindowSceneFBSSceneTransitionContextDrivenLifecycleSettingsDiffAction _performActionsForUIScene:withUpdatedFBSScene:settingsDiff:fromSettings:transitionContext:lifecycleActionType:]_block... + 196 (_UIWindowSceneFBSSceneTransitionContextDrivenLifecycleSettingsDiffAction.m:72)

17  UIKitCore                         0x18e1b6e84 +[BSAnimationSettings(UIKit) tryAnimatingWithSettings:actions:completion:] + 892 (BSAnimationSettings+UIKit.m:50)

18  UIKitCore                         0x18e2c2268 _UISceneSettingsDiffActionPerformChangesWithTransitionContext + 276 (_UISceneSettingsDiffAction.m:23)

19  UIKitCore                         0x18dd485c4 -[_UIWindowSceneFBSSceneTransitionContextDrivenLifecycleSettingsDiffAction _performActionsForUIScene:withUpdatedFBSScene:settingsDiff:fromSettings:transitionContext:lifecycleActionType:] + 384 (_UIWindowSceneFBSSceneTransitionContextDrivenLifecycleSettingsDiffAction.m:57)

20  UIKitCore                         0x18db704ac __64-[UIScene scene:didUpdateWithDiff:transitionContext:completion:]_block_invoke + 776 (UIScene.m:1419)

21  UIKitCore                         0x18db6ee2c -[UIScene _emitSceneSettingsUpdateResponseForCompletion:afterSceneUpdateWork:] + 256 (UIScene.m:1140)

22  UIKitCore                         0x18db700d4 -[UIScene scene:didUpdateWithDiff:transitionContext:completion:] + 248 (UIScene.m:1386)

23  UIKitCore                         0x18e6ea700 -[UIApplication workspace:didCreateScene:withTransitionContext:completion:] + 572 (UIApplication.m:3697)

24  UIKitCore                         0x18e1e04e4 -[UIApplicationSceneClientAgent scene:didInitializeWithEvent:completion:] + 388 (UIApplicationSceneClientAgent.m:45)

25  FrontBoardServices               0x19b2c95d8 -[FBSScene _callOutQueue_agent_didCreateWithTransitionContext:completion:] + 440 (FBSScene.m:435)

26  FrontBoardServices               0x19b2f4d44 __94-[FBSWorkspaceScenesClient createWithSceneID:groupID:parameters:transitionContext:completion:]_block_invoke.200 + 128 (FBSWorkspaceScenesClient.m:365)

27  FrontBoardServices               0x19b2d86a4 -[FBSWorkspace _calloutQueue_executeCalloutFromSource:withBlock:] + 240 (FBSWorkspace.m:355)

28  FrontBoardServices               0x19b2f4a0c __94-[FBSWorkspaceScenesClient createWithSceneID:groupID:parameters:transitionContext:completion:]_block_invoke + 372 (FBSWorkspaceScenesClient.m:364)

29  libdispatch.dylib                 0x18b8e481c _dispatch_client_callout + 20 (object.m:559)

[/SIZE]

 

Thanks for the fix @Alexey

 

I also got an error only in Release Build of ios.
UnityFramework: -[UnityAppController pickStartupWindowScene:]

It was built and updated without any problems until July 2022.
After adding Firebase DynamicLink SDK for Unity (tested 8.1.0, 9.1.0, 9.3.0) in August 2022, the build started having problems.

When I connect iphone in xcode and test by pressing "PlayButton(ReleaseForRunning)" everything works fine.
However, after archiving, uploading and downloading through Test Flight always crashes.

NSAssert(foregroundScene != nil, @"No foreground window scene found at startup");
"Last Exception Backtrace (0)" occurred in this part.

I applied the code you gave me, but this time an error occurred in another part.
else if (scene.activationState == UISceneActivationStateBackground)
"Last Exception Backtrace (0)" occurred in this part.

Because of this, the update on the App Store side has been impossible for two months.
Please tell me how to solve this problem.

Below is a list of my tests, and all of them have the same error.
Unity2020.3.29, 2020.3.38
xcode 13.3, 13.4, 13.4.1
Please give me any hints to solve this.

 

Same here: https://forum.unity.com/threads/uni...-pickstartupwindowscene.1243444/#post-8449919 is it related? we have seen a bump of errors on IOS 16 players that cannot start the game. Nothing has changed in the last 4 months.

 

Hi. Did you find a solution to this?