Search Issue Tracker
Fixed in 2018.3.X
Votes
0
Found in
2018.1.0b8
2018.2.0f2
Issue ID
1067917
Regression
Yes
[IL2CPP] "Unity extensions are not yet initialized" errors are thrown when opening project with Target Platform set to UWP
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.CompilationUnit:CompilationUnits(String)
SyntaxTree.VisualStudio.Unity.Bridge.CompilationUnit:CompilationUnitsForPlayer()
SyntaxTree.VisualStudio.Unity.Bridge.ProjectFilePostprocessor:OnGeneratedSlnSolution(String, String)
UnityEditor.Modules.ModuleManager:RegisterAdditionalUnityExtensions()
Fixed in 2018.3.0b1
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Long Prefab save times when using Unity 2022.2 and higher
- Console displays error "UnityException: Creating asset at path Assets/Scenes/ .scenetemplate failed." during scene template saving
- "Development Build" watermark is shown in non-development UWP release builds
- Console errors appear when the Inspector is set to Debug and a GameObject is selected
- A script public variable value is not used when set in the Inspector window
ventsie
Jun 24, 2019 08:54
+1 for ALEXRAU's comment! I am unable to update, because the assets I am using do not support 2018.3. We need a different solution.
dionysis
Jun 07, 2019 13:53
I saw this error on a system where I had forgotten to install the C++ for UWP Visual Studio components. As soon as I installed those components and restarted Unity, the issue went away.
alexrau
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....