Search Issue Tracker

Active

Votes

10

Found in

2017.2.0b1

Issue ID

923633

Regression

Yes

Unity extensions are not yet initialized assertions at project opening

Scripting

-

-

Priority: 3Not yet prioritized for a release

-

Severity: 3Workaround is possible

Editor throws assertions at project opening

For repro open attached project. It's switched to Universal Windows Platform with scripting runtime version 4.6 and VS 2015 is set as external code editor.

Assertion should appear:

Assertion failed: Unity extensions are not yet initialized, so we cannot say if the 'C:/Program Files/Unity 2017.2.0b1/Editor/Data/UnityExtensions/Unity/UnityHoloLens/Runtime/UnityEngine.HoloLens.dll' is compatible with platform WindowsStoreApps
UnityEditorInternal.InternalEditorUtility:GetPrecompiledAssemblies(Boolean, BuildTargetGroup, BuildTarget)
UnityEditorInternal.InternalEditorUtility:GetMonoIslandsForPlayer() (at C:/buildslave/unity/build/Editor/Mono/InternalEditorUtility.cs:377)
System.Reflection.MethodBase:Invoke(Object, Object[])
SyntaxTree.VisualStudio.Unity.Bridge.CompilationUnit:CompilationUnits(String)
SyntaxTree.VisualStudio.Unity.Bridge.CompilationUnit:CompilationUnitsForPlayer()
SyntaxTree.VisualStudio.Unity.Bridge.ProjectSystem.UnitySolutionBuilder:CreatePlayerProject(CompilationUnit)
SyntaxTree.VisualStudio.Unity.Bridge.ProjectSystem.UnitySolutionBuilder:CreateSolution()
SyntaxTree.VisualStudio.Unity.Bridge.ProjectSystem.UnitySolutionBuilder:CreateSolutionFromAssetDatabase()
SyntaxTree.VisualStudio.Unity.Bridge.ProjectFilesGenerator:GenerateProject()
SyntaxTree.VisualStudio.Unity.Bridge.ProjectFilePostprocessor:OnPreGeneratingCSProjectFiles()
UnityEditor.SyncVS:SyncVisualStudioProjectIfItAlreadyExists()

All about bugs

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