Search Issue Tracker

Fixed in Unity 2018.3



Found in


Issue ID




[IL2CPP] "Unity extensions are not yet initialized" errors are thrown when opening project with Target Platform set to UWP




Priority: 2Necessary for shipping a final release


Severity: 3Secondary functionality broken

How to reproduce:
1. Open the attached project
2. In the Build settings window, switch the target platform to "Universal Windows Platform"
3. Reopen the project

Expected result: Console errors about unity extensions not being initialized are not thrown.
Actual result: Project loads with dozens of console errors about unity extensions not being initialized.

Reproducible with - 2018.1.0b8, 2018.1.9f1, 2018.2.0a1, 2018.2.5f1, 2018.3.0a1, 2018.3.0a9
Not reproducible with - 2017.2.3p3, 2017.4.9f1, 2018.1.0b7

Errors that are thrown:
Unity extensions are not yet initialized, so we cannot say if the <<dll file path>> is compatible with platform WindowsStoreApps
UnityEditorInternal.InternalEditorUtility:GetPrecompiledAssemblies(Boolean, BuildTargetGroup, BuildTarget)
UnityEditorInternal.InternalEditorUtility:GetMonoIslandsForPlayer() (at C:/buildslave/unity/build/Editor/Mono/InternalEditorUtility.cs:396)
System.Reflection.MethodBase:Invoke(Object, Object[])
SyntaxTree.VisualStudio.Unity.Bridge.ProjectFilePostprocessor:OnGeneratedSlnSolution(String, String)

Fixed in 2018.3.0b1

Comments (1)

  1. 14014699f49cf6202ccfea020988a7ed?d=mm


    Dec 18, 2018 01:12

    Not really a fix for those of us who use assets that need work for 2018.3. Wish I could spend more time developing and less time chasing an upgrade path. Maybe if there was a clean way to uninstall assets off asset store....

All about bugs

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