Search Issue Tracker
Fixed in 1.0.11
Votes
0
Found in [Package]
1.0.2
Issue ID
1156795
Regression
Yes
[Visual Studio] .csproj and .sln files are generated incorrectly causing Visual Studio to not understand Unity types
How to reproduce:
1. Open any project in 2019.2.0a12 or above and install Visual Studio Editor package
2. Write any Unity related script in any file (for example something containing GameObjects or Transforms)
-- Observe the console errors
Reproduced with: 2019.3.0a4 with package version 1.0.2 and 1.0.10
Couldn't reproduce on any 2019.2 version with any package version.
Note: Different kind of errors in 2019.3.0a1.
Errors:
NullReferenceException: Object reference not set to an instance of an object
UnityEditor.Experimental.AssetImporters.AssetImporterEditor.InternalSetTargets (UnityEngine.Object[] t) (at C:/buildslave/unity/build/Modules/AssetPipelineEditor/ImportSettings/AssetImporterEditor.cs:122)
UnityEditor.Editor.OnForceReloadInspector () (at C:/buildslave/unity/build/Editor/Mono/Inspector/Editor.cs:603)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Add comment