Search Issue Tracker


Planned for 2019.4, 2020.1, 2020.2



Found in




Issue ID




[iOS][UaaL] UnityFramework with 3rd party plugins triggers watchdog termination after launch



Reproduction steps:
1. Open project in ""
2. Build the project for iOS
3. Open .xcworkspace generated in the build folder
4. Deploy the Application to an iOS device
5. Shut the Application down (using Xcode or the device itself)
6. Open the Application from the device (without using Xcode)

Expected result: the Application will launch successfully
Actual result: the Application starts launching and shuts down in around 10-20 secs

Reproducible with: 2019.3.15f1, 2019.4.5f1, 2020.1.0f1, 2020.2.0a18
Could not test with 2018.4, 2019.3.0a1 because I was unable to resolve package/namespace errors

Devices tested:
Reproducible with:
VLNQA00310 iPad Pro 12.9 1st gen (iOS 13.4.1)
Not reproducible with:
VLNQA00204 iPhone 5C (iOS 10.3.3)
iPhone 7 iOS 12.3.
iPad 7th gen iOS 13.2.2
VLNQA00015, Samsung Galaxy Note8 (SM-N950W), Android 8.0.0, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540

Possible workaround:
By default UnityFramework.framework is embedded to Unity-iPhone target and it is not linked with it. UnityFramework is loaded later at runtime with NSBundle.load and some plugins are sensitive to this initialization path.
* Go to Unity-iPhone / Build Phases / Link Binary with Libraries build section and add UnityFramework.framework.
UnityFramework will be loaded at the same time as the main executable.

Comments (7)

  1. B17cfc5f85f28adb2bb6ef5a8e0cfa95?d=mm


    Oct 13, 2020 12:29

    We have also experienced this issue on tvOS / AppleTV4K running iOS 13.4.8. Linking UnityFramework.framework directly in Unity-iPhone fixes the issue for us.

  2. E38201e055f7186b920654ba5f6baafe?d=mm


    Oct 10, 2020 06:34

    Unity 2019.4.11f1 and Unity 2019.4.12f1 both said they fixed this issue, but unfortunately they didn't.

  3. 4d29c7d78bb724701e3bc6eca5eb0142?d=mm


    Oct 09, 2020 14:00

    The issue was created on Jul 10, 2020, this bug is known on forums months before, and there is still no fix for this?

    All Unity version after February 2020 has this issue, people are losing users because of this. Yes, you can use older Unity, but then that Unity doesn't have other important fixes, for example, fix related to Storyboard that is mandatory since July 2020. What should we do?

    You can't fix this or give some workaround?

    What a shame. Unity is more and more disappointment, spending time on fancy new half-finished features that we can live without, but can't spend time to solve crucial bugs on platforms (mobile) that popularized Unity and it is keeping Unity alive.

  4. C33b0675159d3594e82ee8ae958ae3df?d=mm


    Oct 06, 2020 13:27

    A Question, does this workaround mention works?

  5. C33b0675159d3594e82ee8ae958ae3df?d=mm


    Oct 06, 2020 13:26

    I think this issue is underrated because most of the users would struggle with different crash logs and trying to figure out the issue

  6. 7fd0c474c2e8a071c13746c492beb541?d=mm


    Sep 26, 2020 05:29

    Reproduced on
    - 2018.4.26 / 2018.4.27 / 2019.4.10 on iPhoneX with OS 14.0 / 14.2
    - 2018.4.27 on iPhoneSE with iOS 13
    - plugins: Obi, AppLovin MAX, Firebase(crashlytics, remoteConfig), facebook, admob ...
    - same as following

  7. 4d831347431d4b1bce560b95f071f073?d=mm


    Sep 03, 2020 11:47

    Reproduced on Unity 2019.4.9f1 on iPad 9.7 with OS 13.3.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.