UnityFramework load in 2019.3.11 causes Watchdog Transgression crash (0x8badf00d)

In the most recent Unity version 2019.3.11, a generated XCode project loads UnityFramework on startup. My guess is that it now takes more time to load the app and any third party dependencies that initalize on startup can crash a Unity app on iOS. Here is a related issue on github for firebase sdk https://github.com/firebase/firebase-ios-sdk/issues/5463

Here is an example, adding Firebase SDK to my app adds following lines to the crash stack

Code (CSharp):

1. 17  UnityFramework                    0x000000010b28e8c4 +[GDTCORReachability sharedInstance] + 4270276 (GDTCORReachability.m:53)
2. 18  UnityFramework                    0x000000010b28e878 +[GDTCORReachability load] + 4270200 (GDTCORReachability.m:0)
3. 19  libobjc.A.dylib                   0x00000001a8c3435c load_images + 984

If I add a Fyber Ad sdk, it adds following lines:

Code (CSharp):

1.   UnityFramework                    0x0000000109107350 +[IAAdRequestHelper sharedInstance] + 5927760 (IAAdRequestHelper.m:50)
2. 28  UnityFramework                    0x00000001091072d4 +[IAAdRequestHelper load] + 5927636 (IAAdRequestHelper.m:0)

Adding one of the dependencies or both of them can cause a crash. Updating the source code of GDTCORReachability in Firebase SDK and replacing the load call to initialize solves the issue. All dependencies work fine in projects generated by older versions of Unity.

Is there anything that can be addressed in the Unity project, so dependencies wouldn't crash the app?

Here is the full crash report

Code (CSharp):

1. Exception Codes: 0x0000000000000000, 0x0000000000000000
2. Exception Note:  EXC_CORPSE_NOTIFY
3. Termination Reason: Namespace SPRINGBOARD, Code 0x8badf00d
4. Termination Description: SPRINGBOARD, process-launch watchdog transgression: application<com. . >:1978 exhausted real (wall clock) time allowance of 20.00 seconds | ProcessVisibility: Unknown | ProcessState: Running | WatchdogEvent: process-launch | WatchdogVisibility: Foreground | WatchdogCPUStatistics: ( | "Elapsed total CPU time (seconds): 3.880 (user 3.880, system 0.000), 10% CPU", | "Elapsed application CPU time (seconds): 0.185, 0% CPU" | )
5. Triggered by Thread:  0
6.  
7. Thread 0 name:  Dispatch queue: com.apple.main-thread
8. Thread 0 Crashed:
9. 0   libsystem_kernel.dylib            0x00000001a8cff77c __ulock_wait + 8
10. 1   libdispatch.dylib                 0x00000001a8b760a8 _dlock_wait + 52
11. 2   libdispatch.dylib                 0x00000001a8b75fe8 _dispatch_once_wait$VARIANT$mp + 112
12. 3   libnetwork.dylib                  0x00000001ab39779c nw_parameters_copy_description + 2144
13. 4   libnetwork.dylib                  0x00000001ab396e64 -[NWConcrete_nw_parameters description] + 12
14. 5   Foundation                        0x00000001a92d6058 _NS_os_log_callback + 224
15. 6   libsystem_trace.dylib             0x00000001a8ab0338 _os_log_fmt_flatten_NSCF + 60
16. 7   libsystem_trace.dylib             0x00000001a8aafb34 _os_log_fmt_flatten_object + 212
17. 8   libsystem_trace.dylib             0x00000001a8abc244 _os_log_impl_flatten_and_send + 1756
18. 9   libnetwork.dylib                  0x00000001ab4f0e00 nw_path_evaluator_start + 1604
19. 10  libnetwork.dylib                  0x00000001ab4f2520 nw_path_evaluator_set_update_handler + 216
20. 11  SystemConfiguration               0x00000001a9176bcc __SCNetworkReachabilitySetDispatchQueue + 768
21. 12  SystemConfiguration               0x00000001a9176e24 SCNetworkReachabilitySetDispatchQueue + 120
22. 13  UnityFramework                    0x000000010b28eadc -[GDTCORReachability init] + 4270812 (GDTCORReachability.m:83)
23. 14  UnityFramework                    0x000000010b28e8e8 __36+[GDTCORReachability sharedInstance]_block_invoke + 4270312 (GDTCORReachability.m:54)
24. 15  libdispatch.dylib                 0x00000001a8bcf524 _dispatch_client_callout + 16
25. 16  libdispatch.dylib                 0x00000001a8b76dc8 _dispatch_once_callout + 28
26. 17  UnityFramework                    0x000000010b28e8c4 +[GDTCORReachability sharedInstance] + 4270276 (GDTCORReachability.m:53)
27. 18  UnityFramework                    0x000000010b28e878 +[GDTCORReachability load] + 4270200 (GDTCORReachability.m:0)
28. 19  libobjc.A.dylib                   0x00000001a8c3435c load_images + 984
29. 20  libdyld.dylib                     0x00000001a8d17d3c invocation function for block in dyld3::AllImages::runInitialzersBottomUp+ 64828 (dyld3::closure::Image const*) + 220
30. 21  libdyld.dylib                     0x00000001a8d0b064 dyld3::closure::Image::forEachImageToInitBefore(void + 12388 (unsigned int, bool&) block_pointer) const + 92
31. 22  libdyld.dylib                     0x00000001a8d186a0 dyld3::AllImages::loadImage+ 67232 (Diagnostics&, unsigned int, dyld3::closure::DlopenClosure const*, bool, bool, bool, bool) + 612
32. 23  libdyld.dylib                     0x00000001a8d182a8 dyld3::AllImages::dlopen+ 66216 (Diagnostics&, char const*, bool, bool, bool, bool, bool, void const*) + 848
33. 24  libdyld.dylib                     0x00000001a8d19b74 dyld3::dlopen_internal+ 72564 (char const*, int, void*) + 360
34. 25  libdyld.dylib                     0x00000001a8d0d8d8 dlopen + 108
35. 26  CoreFoundation                    0x00000001a8f10218 _CFBundleDlfcnLoadFramework + 136
36. 27  CoreFoundation                    0x00000001a8e38428 _CFBundleLoadExecutableAndReturnError + 424
37. 28  Foundation                        0x00000001a91fe204 -[NSBundle loadAndReturnError:] + 312
38. 29                          0x0000000104fe80c0 UnityFrameworkLoad() + 16576 (main.mm:12)
39. 30                          0x0000000104fe81b4 main + 16820 (main.mm:0)
40. 31  libdyld.dylib                     0x00000001a8d09800 start + 4
41.  

 

Same issue happened on 2019.3.9f1 with Firebase SDK 6.12.0 ~ 6.14.0, attached is my crash log

Code (CSharp):

1.  
2. Incident Identifier: 63A9B753-1C0A-457D-AF1F-5F17B64D4861
3. CrashReporter Key:   911e3a309e89c75e9deb1f72b4d92e261847b02a
4. Hardware Model:      iPhone10,1
5. Process:             game [16385]
6. Path:                /private/var/containers/Bundle/Application/FFED1A38-8F94-49E2-8057-78A2E544CDB7/game.app/game
7. Identifier:          com.rabc.word.game
8. Version:             0 (2.2.2)
9. Code Type:           ARM-64 (Native)
10. Role:                Foreground
11. Parent Process:      launchd [1]
12. Coalition:           com.rabc.word.game [3512]
13.  
14.  
15. Date/Time:           2020-04-27 19:18:03.7249 +0800
16. Launch Time:         2020-04-27 19:17:43.6781 +0800
17. OS Version:          iPhone OS 13.3.1 (17D50)
18. Release Type:        User
19. Baseband Version:    5.30.01
20. Report Version:      104
21.  
22. Exception Type:  EXC_CRASH (SIGKILL)
23. Exception Codes: 0x0000000000000000, 0x0000000000000000
24. Exception Note:  EXC_CORPSE_NOTIFY
25. Termination Reason: Namespace SPRINGBOARD, Code 0x8badf00d
26. Termination Description: SPRINGBOARD, process-launch watchdog transgression: application<com.rabc.word.game>:16385 exhausted real (wall clock) time allowance of 20.00 seconds | ProcessVisibility: Unknown | ProcessState: Running | WatchdogEvent: process-launch | WatchdogVisibility: Foreground | WatchdogCPUStatistics: ( | "Elapsed total CPU time (seconds): 5.370 (user 5.370, system 0.000), 4% CPU", | "Elapsed application CPU time (seconds): 0.128, 0% CPU" | )
27. Triggered by Thread:  0
28.  
29. Thread 0 name:  Dispatch queue: com.apple.main-thread
30. Thread 0 Crashed:
31. 0   libsystem_kernel.dylib            0x000000019b5d68b8 __ulock_wait + 8
32. 1   libdispatch.dylib                 0x000000019b47d2a8 _dlock_wait + 52
33. 2   libdispatch.dylib                 0x000000019b47d1f0 _dispatch_once_wait$VARIANT$armv81 + 120
34. 3   UnityFramework                    0x0000000104a3fa34 +[GDTCORReachability sharedInstance] + 2357812 (once.h:85)
35. 4   UnityFramework                    0x0000000104a3f9ec +[GDTCORReachability load] + 2357740 (GDTCORReachability.m:0)
36. 5   libobjc.A.dylib                   0x000000019b50de78 load_images + 908
37. 6   libdyld.dylib                     0x000000019b5ee994 invocation function for block in dyld3::AllImages::runInitialzersBottomUp+ 63892 (dyld3::closure::Image const*) + 220
38. 7   libdyld.dylib                     0x000000019b5e1bbc dyld3::closure::Image::forEachImageToInitBefore(void + 11196 (unsigned int, bool&) block_pointer) const + 92
39. 8   libdyld.dylib                     0x000000019b5ef2d0 dyld3::AllImages::loadImage+ 66256 (Diagnostics&, unsigned int, dyld3::closure::DlopenClosure const*, bool, bool, bool, bool) + 612
40. 9   libdyld.dylib                     0x000000019b5eee58 dyld3::AllImages::dlopen+ 65112 (Diagnostics&, char const*, bool, bool, bool, bool, bool, void const*) + 680
41. 10  libdyld.dylib                     0x000000019b5f07a4 dyld3::dlopen_internal+ 71588 (char const*, int, void*) + 360
42. 11  libdyld.dylib                     0x000000019b5e4420 dlopen + 108
43. 12  CoreFoundation                    0x000000019b7e56e0 _CFBundleDlfcnLoadFramework + 136
44. 13  CoreFoundation                    0x000000019b70ce80 _CFBundleLoadExecutableAndReturnError + 424
45. 14  Foundation                        0x000000019bad03bc -[NSBundle loadAndReturnError:] + 312
46. 15  game                              0x0000000102527d38 UnityFrameworkLoad() + 32056 (main.mm:12)
47. 16  game                              0x0000000102527de0 main + 32224 (main.mm:0)
48. 17  libdyld.dylib                     0x000000019b5e0360 start + 4
49.  
50.  

 

Same issue
Startup can crash a Unity app on iOS.
Does work fine on devices with ios 13.3+
Crashes on ios 10

2019.3.8
and
2019.3.11

 

Can confirm this is also happening in 2019.3.6f1, and is crashing on iOS 13.3.1.

 

I don't see this issue if I build a UnityFramework and reference it in a different XCode project, that loads Unity from the AppDelegate.

Instead of loading Unity like this

Code (CSharp):

1.  // run UnityFramework as main app
2.             id ufw = UnityFrameworkLoad();
3.  
4.             // Set UnityFramework target for Unity-iPhone/Data folder to make Data part of a UnityFramework.framework and call to setDataBundleId
5.             // ODR is not supported in this case, ( if you need embedded and ODR you need to copy data )
6.             [ufw setDataBundleId: "com.unity3d.framework"];
7.             [ufw runUIApplicationMainWithArgc: argc argv: argv];

I load the AppDelegate first and then initialize Unity from it

Code (CSharp):

1. UIApplicationMain(argc, argv, nil, [NSString stringWithUTF8String: "AppDelegate"]);

 

It looks like it only affects Unity 2019.3, works fine with Unity 2019.2

 

Here is an update from the Firebase team: "We think that this is a unity bug that's triggered when SCNetworkReachabilitySetDispatchQueue is called during +(void)load. We've removed our reachability calls from +load to +initialize in the hopes it will help out, but Unity may need to take some action as well. Thanks for all the great debugging everyone!"

https://github.com/firebase/firebase-ios-sdk/issues/5463#issuecomment-621445302

Unity 2019.3 on iOS is a mess, something needs to be done about it

 

Hello,
I am having the exact same issue using 2019.3

I have updated the firebase.database to the latest version, I checked that SCNetworkReachabilitySetDispatchQueue is called on initialise in the SDK, but I am still having the issue in some iOS devices.

Has the new SDK worked for everybody else or this is just me?
Thanks

 

Hello.
The same crash happen on Unity 2019.3.12. I am using fribase.database and firbase.auth.

 

Hello @DevOlzhas I managed to fix the problem by following this post:
https://github.com/firebase/firebase-ios-sdk/issues/5463#issuecomment-622274271

It is a work around though. My database does not need that line apparently. but I will still follow up in the firebase github account for future releases and fixes
I hope this helps

 

i am facing similar issue in Unity 2018.4.21f1.

{"app_name":"theloungerz","timestamp":"2020-05-11 17:49:43.32 +0530","app_version":"1.0","slice_uuid":"bcceb065-492d-3f07-af57-3cf2723abe3d","adam_id":0,"build_version":"16","bundleID":"games.spontom.theloungerz","share_with_app_devs":true,"is_first_party":false,"bug_type":"109","os_version":"iPhone OS 13.3.1 (17D50)","incident_id":"B6887DAC-0A40-41F4-A610-FD0545D5A28F","name":"theloungerz"}
Incident Identifier: B6887DAC-0A40-41F4-A610-FD0545D5A28F
CrashReporter Key: 2650223b012475d4cf45a6ff875aead981773466
Hardware Model: iPad5,3
Process: theloungerz [1935]
Path: /private/var/containers/Bundle/Application/3707E949-2069-49C0-8346-24B2D6ED87BA/theloungerz.app/theloungerz
Identifier: games.spontom.theloungerz
Version: 16 (1.0)
Code Type: ARM-64 (Native)
Role: Non UI
Parent Process: launchd [1]
Coalition: games.spontom.theloungerz [1385]


Date/Time: 2020-05-11 17:49:43.0476 +0530
Launch Time: 2020-05-11 17:49:32.2554 +0530
OS Version: iPhone OS 13.3.1 (17D50)
Release Type: User
Baseband Version: n/a
Report Version: 104

Exception Type: EXC_CRASH (SIGKILL)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Termination Reason: Namespace SPRINGBOARD, Code 0x8badf00d
Termination Description: SPRINGBOARD, process-exit watchdog transgression: application<games.spontom.theloungerz>:1935 exhausted real (wall clock) time allowance of 5.00 seconds | ProcessVisibility: Unknown | ProcessState: Running | WatchdogEvent: process-exit | WatchdogVisibility: Foreground | WatchdogCPUStatistics: ( | "Elapsed total CPU time (seconds): 4.080 (user 4.080, system 0.000), 27% CPU", | "Elapsed application CPU time (seconds): 0.196, 1% CPU" | )
Triggered by Thread: 0

Thread 0 name: Dispatch queue: com.apple.main-thread
Thread 0 Crashed:
0 libsystem_kernel.dylib 0x00000001bad0bc94 __psynch_cvwait + 8
1 libsystem_pthread.dylib 0x00000001bac28d2c _pthread_cond_wait$VARIANT$mp + 732
2 theloungerz 0x0000000101547e88 il2cpp:s:osix:osixWaitObject::Wait(unsigned int, bool) + 13860488 (PosixWaitObject.cpp:159)
3 theloungerz 0x000000010153f524 il2cpp:s::Thread::Join(unsigned int) + 13825316 (Thread.cpp:212)
4 theloungerz 0x000000010155dce4 il2cpp::vm::Thread::KillAllBackgroundThreadsAndWaitForForegroundThreads() + 13950180 (Thread.cpp:305)
5 theloungerz 0x0000000101566b40 il2cpp::vm::Runtime::Shutdown() + 13986624 (Runtime.cpp:428)
6 theloungerz 0x0000000100ffac80 CleanupIl2Cpp() + 8301696 (MonoManager_Il2Cpp.cpp:279)
7 theloungerz 0x0000000100f6053c PlayerCleanup(bool) + 7669052 (Player.cpp:611)
8 theloungerz 0x0000000101167888 UnityCleanup + 9795720 (LibEntryPoint.mm:227)
9 theloungerz 0x000000010082c3d8 -[UnityAppController applicationWillTerminate:] + 115672 (UnityAppController.mm:424)
10 UIKitCore 0x00000001bef9fae0 -[UIApplication _terminateWithStatus:] + 244
11 UIKitCore 0x00000001be7658b8 -[_UISceneLifecycleMultiplexer _evalTransitionToSettings:fromSettings:forceExit:withTransitionStore:] + 124
12 UIKitCore 0x00000001be765538 -[_UISceneLifecycleMultiplexer forceExitWithTransitionContext:scene:] + 216
13 UIKitCore 0x00000001bef95e80 -[UIApplication workspaceShouldExit:withTransitionContext:] + 212
14 FrontBoardServices 0x00000001c004090c -[FBSUIApplicationWorkspaceShim workspaceShouldExit:withTransitionContext:] + 84
15 FrontBoardServices 0x00000001c006c05c __83-[FBSWorkspaceScenesClient willTerminateWithTransitionContext:withAcknowledgement:]_block_invoke_2 + 76
16 FrontBoardServices 0x00000001c0051f04 -[FBSWorkspace _calloutQueue_executeCalloutFromSource:withBlock:] + 232
17 FrontBoardServices 0x00000001c006bfec __83-[FBSWorkspaceScenesClient willTerminateWithTransitionContext:withAcknowledgement:]_block_invoke + 124
18 libdispatch.dylib 0x00000001babe1184 _dispatch_client_callout + 16
19 libdispatch.dylib 0x00000001bab89fd8 _dispatch_block_invoke_direct$VARIANT$mp + 224
20 FrontBoardServices 0x00000001c0091418 __FBSSERIALQUEUE_IS_CALLING_OUT_TO_A_BLOCK__ + 40
21 FrontBoardServices 0x00000001c00910e4 -[FBSSerialQueue _queue_performNextIfPossible] + 404
22 FrontBoardServices 0x00000001c009160c -[FBSSerialQueue _performNextFromRunLoopSource] + 28
23 CoreFoundation 0x00000001bae92a00 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 24
24 CoreFoundation 0x00000001bae92958 __CFRunLoopDoSource0 + 80
25 CoreFoundation 0x00000001bae920f0 __CFRunLoopDoSources0 + 180
26 CoreFoundation 0x00000001bae8d23c __CFRunLoopRun + 1080
27 CoreFoundation 0x00000001bae8cadc CFRunLoopRunSpecific + 464
28 GraphicsServices 0x00000001c4e2d328 GSEventRunModal + 104
29 UIKitCore 0x00000001bef9a63c UIApplicationMain + 1936
30 theloungerz 0x0000000100815c30 main + 23600 (main.mm:41)
31 libdyld.dylib 0x00000001bad16360 start + 4

Thread 1:
0 libsystem_pthread.dylib 0x00000001bac33758 start_wqthread + 0

Thread 2:
0 libsystem_pthread.dylib 0x00000001bac33758 start_wqthread + 0

Thread 3:
0 libsystem_pthread.dylib 0x00000001bac33758 start_wqthread + 0

 

I am also facing the same crash. It is very random, does not happen every time. I am using Firebase SDK 6.14.0 and Unity 2019.3.11f1. Device iOS version 13.3.1, I can't roll back to older Unity version because older versions has the UIWebView issue that was causing app rejection for me. I don't know how you guys are getting your apps approved by Apple while using older Unity versions. So I am kind of stuck unity Firebase of Unity releases a fix. Is there a solution for this in Unity 2019.3.x?

 

Firebase 6.15 should fix this issue. Its scheduled for release this week. You can follow the issue here: https://github.com/firebase/firebase-ios-sdk/issues/5463#issuecomment-633651947

 

Firebase is ping-ponging it back to Unity. I'm gonna grab some popcorn

 

I found a solution, you just need to update your pod.

firebase authorization, database, core
Version 6.25

 

Thanks for the update. The unity plugin itself doesn't seem to be updated yet, so I'll just wait for that

 

Has anyone posted a bug report about this so we can surface it to Unity employees? @yurykorzun @nicolasgramlich @ismailmardin10 @Benfont @Dazo1985

I've also seen the same issue, but checking in here before I make a duplicate bug report...

 

I have not posted an official bug. I was going to wait until 6.25.0 unity package dropped to see if that fixes it.

 

I could not find the 6.25 version of the Firebase plugin. Sorry, I could not understand how changing the pod will get that version. Can you please tell me how did you find out there is a 6.25 version available through pod?

 

Only 6.14.1 is available in package manager

 

So even

6.14.0

of the Unity plugin uses

6.21.0

(at the time I ran it at least) of the ios FB pods, which was released March 24, 2020:

Code (CSharp):

1. source 'https://github.com/CocoaPods/Specs.git'
2. source 'https://github.com/CocoaPods/Specs'
3. platform :ios, '10.0'
4.  
5. target 'UnityFramework' do
6.   pod 'Crashlytics', '3.14.0'
7.   pod 'Fabric', '1.10.2'
8.   pod 'FBSDKCoreKit', '~> 6.2'
9.   pod 'FBSDKGamingServicesKit', '~> 6.2'
10.   pod 'FBSDKLoginKit', '~> 6.2'
11.   pod 'FBSDKShareKit', '~> 6.2'
12.   pod 'Firebase/Analytics', '6.21.0'
13.   pod 'Firebase/Auth', '6.21.0'
14.   pod 'Firebase/Core', '6.21.0'
15.   pod 'Firebase/Database', '6.21.0'
16.   pod 'Firebase/DynamicLinks', '6.21.0'
17.   pod 'Firebase/Firestore', '6.21.0'
18.   pod 'Firebase/Functions', '6.21.0'
19.   pod 'Firebase/Messaging', '6.21.0'
20.   pod 'Firebase/RemoteConfig', '6.21.0'
21.   pod 'Firebase/Storage', '6.21.0'
22.   pod 'FirebaseInstanceID', '4.3.2'
23.   pod 'GoogleMobileAdsMediationFacebook', '5.8.0.2'
24.   pod 'GoogleMobileAdsMediationUnity', '3.4.2.1'
25.   pod 'Google-Mobile-Ads-SDK', '~> 7.58'
26.   pod 'GoogleSignIn', '>= 5.0.0'
27. end

So I was hoping that they'd eventually update it themselves, or if need be one could probably just update the podfile itself to point to

6.25.0

. If they followed semver convention, there shouldn't have been any breaking changes between

6.21.0

and

6.25.0

.

 

first step find your xcode build location and double click podfile or edit
https://ibb.co/r6ZBQk9
second step then save the podfile as pictured
https://ibb.co/d5fZZFv

third step Go to the location where your podfile file is with the terminal and type pod update at the command line and enter
https://ibb.co/QX5208M
After the update is over. go build and, problem solved

 

We don't use Firebase and also have this error with 2019.3.14f1, 2019.3.15f1. Used plugins are AppsFlyer SDK, IronSource SDK with integrations through pods( Fyber SDK, Facebook SDK, Facebook Audience Network, AdMob, Mintagral, Amazon, InMobi, Vungle, Pangle, etc).

The only thing that helped was downgrading to 2019.2.21f1 . Interested in other solutions as well

 

Just add this xml file to any Editor folder. It makes PlayServicesResolver use 6.25 version of Firebase. This seem to help me...

 

Hey guys, talking about Fyber SDK here. We fixed this Unity 2019.3 issue from version 7.55 (https://marketplace-supply.fyber.com/docs/ios-changelog#version-755)
Make sure that the mediation you're using has the right adapter to support Fyber v7.55 or later
If you are using Fyber mediation product, the fix is embedded from version FairBid 3.2.0 (https://dev-unity.fyber.com/docs/fairbid-sdk#version-320)

 

Does the Unity Firebase 6.15 Update solve anything? (It looks like its using 6.24 ios dependency)

 

Firebase 6.15.0 appears to have solved the problem!
https://firebase.google.com/support/release-notes/unity#version_6150_-_june_2_2020

 

I'm seeing a ton of new crashes in Firebase 6.15.0. I see this warning:

WARNING: Future with handle 1 still exists though its backing API 0x64B18070 is being deleted. Please call Future::Release() before deleting the backing API.

from this line:

Code (CSharp):

1.         DatabaseReference userStatusDatabaseRef = FirebaseDatabase.DefaultInstance.GetReference("/status/" + uid);
2.  

And then on the next editor play, it crashes. Gonna have to roll back to .14.1.

 

I was part of the original thread and after updating Firebase to 6.15.0 I was still having issues. Therefore I removed all Firebase packages so Firebase is no longer used in my project and I am still having issues. That said I noticed in UnityFramework there are still references to Crashlytics and Firebase.

I have no idea what is causing this issue but I am unable to downgrade Unity at this moment in time. I also removed other packages such as AppCenter and I still have the issue. If I run the app through Xcode onto my device it works fine. As soon as I disconnect my device a re-open the app I get the SIGKILL error again.

Im at a complete loss with this issue so if anybody has any other suggestions that would be great.

 

That's really odd. Maybe have Unity recreate the Xcode project. And if that doesn't help, maybe kill your Libraries/Temp/etc.. folder. (Make sure your actual code is backed up!)

 

Is this the same issue? I upgraded to Firebase 6.15 but still see this crash.

Thanks,
Ash

Termination Reason: Namespace SPRINGBOARD, Code 0x8badf00d
Termination Description: SPRINGBOARD, process-exit watchdog transgression: application< >:436 exhausted real (wall clock) time allowance of 5.00 seconds | ProcessVisibility: Unknown | ProcessState: Running | WatchdogEvent: process-exit | WatchdogVisibility: Foreground | WatchdogCPUStatistics: ( | "Elapsed total CPU time (seconds): 5.390 (user 5.390, system 0.000), 36% CPU", | "Elapsed application CPU time (seconds): 4.532, 30% CPU" | )
Triggered by Thread: 0

 

I still got this problem after updating to Firebase 6.15.0.
What solved it for me is to remove the [sharedUploader startTime] line in GDTCORUploadCoordinator.m in GoogleDataTransport pod.

 

I can't see anything related to this issue in the change log.

 

Did someone happen to check build with Unity 2019.4.0f1 ?

 

Just to confirm, 6.15.0 fixed the issue in the end. It turned out another plugin was also at fault too. UIWebView. Once these were fixed it exported and archived correctly.

 

@stueep

I did not use any firebase plugins ,im getting errors from app review team,submitted 2 times ,got same reply from review,could you suggest how to remove these exceptions of EXC_CRASH (SIGKILL) and EXC_CORPSE_NOTIFY, im using unity 2019.3.15

 

Unfortunately not. The issue is still there.

 

We are experiencing this issue as well on 6.15.0 Unity 2018.4.22f MacOS

 

6.15.0 DIDN'T fixed the issue at all.
Bug still exists, nothing fixed.

 

What are you talking about ?
We are not talking about been able to export and archive, but about a crash.
We are not talking about rejection from Apple of libraries that contains UIWebView.

 

I have the same bug on my game. I'm using IronSource SDK , any news about how to fix this bug ? Thanks a lot

 

Problem is still here. With Firebase 16.5.2 we got same crash. Crash log is little bit different, but i again see firebase in logs

Code (JavaScript):

1. Incident Identifier: 8500A8AA-EEF6-40FA-A814-AECE63E4A787
2. CrashReporter Key:   ad2dd7f79e38f935a8f8a872c060fbed5d61b1e6
3. Hardware Model:      iPhone12,1
4. Process:             avvy [13127]
5. Path:                /private/var/containers/Bundle/Application/EBB4A886-0DA6-4C66-A56A-EBF541DD5B55/avvy.app/avvy
6. Identifier:          com.domido.avvy
7. Version:             27 (2.2.2)
8. Code Type:           ARM-64 (Native)
9. Role:                Foreground
10. Parent Process:      launchd [1]
11. Coalition:           com.domido.avvy [4569]
12.  
13.  
14. Date/Time:           2020-07-14 09:59:44.2945 +0300
15. Launch Time:         2020-07-14 09:59:24.2229 +0300
16. OS Version:          iPhone OS 13.5.1 (17F80)
17. Release Type:        User
18. Baseband Version:    1.06.00
19. Report Version:      104
20.  
21. Exception Type:  EXC_CRASH (SIGKILL)
22. Exception Codes: 0x0000000000000000, 0x0000000000000000
23. Exception Note:  EXC_CORPSE_NOTIFY
24. Termination Reason: Namespace SPRINGBOARD, Code 0x8badf00d
25. Termination Description: SPRINGBOARD, process-launch watchdog transgression: application<com.domido.avvy>:13127 exhausted real (wall clock) time allowance of 20.00 seconds | ProcessVisibility: Unknown | ProcessState: Running | WatchdogEvent: process-launch | WatchdogVisibility: Foreground | WatchdogCPUStatistics: ( | "Elapsed total CPU time (seconds): 5.820 (user 5.820, system 0.000), 5% CPU", | "Elapsed application CPU time (seconds): 0.188, 0% CPU" | )
26. Triggered by Thread:  0
27.  
28. Thread 0 name:  Dispatch queue: com.apple.main-thread
29. Thread 0 Crashed:
30. 0   libsystem_kernel.dylib            0x00000001923577e4 __ulock_wait + 8
31. 1   libdispatch.dylib                 0x0000000192210cd8 _dlock_wait + 56
32. 2   libdispatch.dylib                 0x0000000192210c10 _dispatch_once_wait + 124
33. 3   CFNetwork                         0x0000000195818e9c 0x195806000 + 77468
34. 4   UnityFramework                    0x000000010365318c -[GDTCCTUploader init] + 6631820 (GDTCCTUploader.m:0)
35. 5   UnityFramework                    0x000000010365310c __32+[GDTCCTUploader sharedInstance]_block_invoke + 6631692 (GDTCCTUploader.m:65)
36. 6   libdispatch.dylib                 0x000000019221033c _dispatch_client_callout + 20
37. 7   libdispatch.dylib                 0x0000000192211a68 _dispatch_once_callout + 32
38. 8   UnityFramework                    0x00000001036530e8 +[GDTCCTUploader sharedInstance] + 6631656 (GDTCCTUploader.m:64)
39. 9   UnityFramework                    0x0000000103652fec +[GDTCCTUploader load] + 6631404 (GDTCCTUploader.m:0)
40. 10  libobjc.A.dylib                   0x000000019228dbe0 load_images + 952
41. 11  libdyld.dylib                     0x000000019237052c invocation function for block in dyld3::AllImages::runInitialzersBottomUp+ 66860 (dyld3::closure::Image const*) + 224
42. 12  libdyld.dylib                     0x0000000192362c98 dyld3::closure::Image::forEachImageToInitBefore(void + 11416 (unsigned int, bool&) block_pointer) const + 104
43. 13  libdyld.dylib                     0x0000000192370f10 dyld3::AllImages::loadImage+ 69392 (Diagnostics&, unsigned int, dyld3::closure::DlopenClosure const*, bool, bool, bool, bool) + 652
44. 14  libdyld.dylib                     0x0000000192370adc dyld3::AllImages::dlopen+ 68316 (Diagnostics&, char const*, bool, bool, bool, bool, bool, void const*) + 868
45. 15  libdyld.dylib                     0x0000000192372524 dyld3::dlopen_internal+ 75044 (char const*, int, void*) + 364
46. 16  libdyld.dylib                     0x00000001923657b0 dlopen + 116
47. 17  CoreFoundation                    0x00000001925779e8 _CFBundleDlfcnLoadFramework + 140
48. 18  CoreFoundation                    0x000000019249a194 _CFBundleLoadExecutableAndReturnError + 432
49. 19  Foundation                        0x0000000192869c18 -[NSBundle loadAndReturnError:] + 316
50. 20  avvy                              0x0000000100697d54 UnityFrameworkLoad() + 32084 (main.mm:12)
51. 21  avvy                              0x0000000100697dfc main + 32252 (main.mm:0)
52. 22  libdyld.dylib                     0x00000001923612dc start + 4
53.  
54. Thread 1 name:  Dispatch queue: com.microsoft.appcenter.ChannelGroupQueue
55. Thread 1:
56. 0   libsystem_kernel.dylib            0x0000000192356c10 __psynch_mutexwait + 8
57. 1   libsystem_pthread.dylib           0x000000019227a808 _pthread_mutex_firstfit_lock_wait + 92
58. 2   libsystem_pthread.dylib           0x000000019227a778 _pthread_mutex_firstfit_lock_slow + 260
59. 3   libdyld.dylib                     0x0000000192372404 dyld3::dlopen_internal+ 74756 (char const*, int, void*) + 76
60. 4   libdyld.dylib                     0x00000001923657b0 dlopen + 116
61. 5   CFNetwork                         0x00000001959b4a74 0x195806000 + 1763956
62. 6   libdispatch.dylib                 0x000000019221033c _dispatch_client_callout + 20
63. 7   libdispatch.dylib                 0x0000000192211a68 _dispatch_once_callout + 32
64. 8   CFNetwork                         0x00000001959b4a38 0x195806000 + 1763896
65. 9   CFNetwork                         0x00000001958109b8 0x195806000 + 43448
66. 10  CFNetwork                         0x0000000195817c54 0x195806000 + 72788
67. 11  CFNetwork                         0x0000000195a4c3d0 0x195806000 + 2384848
68. 12  libdispatch.dylib                 0x000000019221033c _dispatch_client_callout + 20
69. 13  libdispatch.dylib                 0x0000000192211a68 _dispatch_once_callout + 32
70. 14  CFNetwork                         0x0000000195818e9c 0x195806000 + 77468
71. 15  AzureSpatialAnchors               0x000000010d011008 0x10c9c4000 + 6606856
72. 16  AzureSpatialAnchors               0x000000010d00fe90 0x10c9c4000 + 6602384
73. 17  AzureSpatialAnchors               0x000000010d0115ec 0x10c9c4000 + 6608364
74. 18  AzureSpatialAnchors               0x000000010d002238 0x10c9c4000 + 6545976
75. 19  AzureSpatialAnchors               0x000000010d021d34 0x10c9c4000 + 6675764
76. 20  AzureSpatialAnchors               0x000000010d00c5bc 0x10c9c4000 + 6587836
77. 21  AzureSpatialAnchors               0x000000010d021914 0x10c9c4000 + 6674708
78. 22  libdispatch.dylib                 0x000000019220eec4 _dispatch_call_block_and_release + 32
79. 23  libdispatch.dylib                 0x000000019221033c _dispatch_client_callout + 20
80. 24  libdispatch.dylib                 0x000000019221685c _dispatch_lane_serial_drain + 568
81. 25  libdispatch.dylib                 0x0000000192217290 _dispatch_lane_invoke + 400
82. 26  libdispatch.dylib                 0x0000000192220928 _dispatch_workloop_worker_thread + 584
83. 27  libsystem_pthread.dylib           0x0000000192277714 _pthread_wqthread + 276
84. 28  libsystem_pthread.dylib           0x000000019227d9c8 start_wqthread + 8

 

I downgraded to Unity 2019.2 to solve those issues.
My D0 retention dropped from 25% to 3%.

 

... This bug affect a lot the retention ... Unfortunately, I cannot downgrade to Unity 2019.2, I use URP

 

I can't find bug about that issue in Unity issue tracker. Is it exists?! How can we draw attention to this issue?

 

Encountered this issue in a third party plugin (not firebase), and had to downgrade to Unity 2019.2 to fix the issue.

 

Same here, I used a third party plugin (not Firebase) and had to downgrade to Unity 2019.2 from Unity 2019.3

 

The issue is possibly not on side of Unity. Starting from version 2019.3, Unity uses a different initialization path, using a framework (iOS library) that embed everything. They had to change their code that manage app's startup. This change revealed existing issues in third party libraries, that just didn't raised until that change. Some fixes have to be made by third parties as well.

Those are mainly dead locks issues (method that is waiting for a locked resource, while another thread is also locking waiting for the same resource). Those deadlocks aren't infinite, but accumulate too much time at startup, which is the reason why the iOS watchdog protection crashes the application (I don't know the exact timing, but your main thread has to be responsive in a 10s window or something like that).

For that reason the difference between the same app startup durations when built against 2019.3 or 2019.2 is blatant : 2019.3 is very slow (like 10 to 15s) while 2019.2 is fast ( less than 3s ).

Being random (sometime deadlocks are 'short enough', thus not crashing the app that just starts with a very slow startup) makes it really hard to reproduce, and thus to be given for correction to 3rd parties.

Also because the crash is at startup, both App Store Connect and Crash-analytics (or Unity crash handler I believe) won't report it. It is totally silent. The app just didn't started.

But you might see it on your retention KPI, and I did see a 30% D1 drop to a 5% D1. When people can't start your game, they pass to another.

 

Looks like this reported issue is the one we are talking about here : https://issuetracker.unity3d.com/is...ns-triggers-watchdog-termination-after-launch

 

Any updates on this? Anybody found any solution.

Does the workaround mention in https://issuetracker.unity3d.com/is...047.413637617.1601901013-225196644.1542053313 works?