Search Issue Tracker
Duplicate
Votes
0
Found in
2017.1.0b1
Issue ID
902684
Regression
Yes
NullReferenceException when importing TextMesh Pro A$ package
1. What happened
During importing 'TextMesh Pro' Asset Store package I'm getting the following errors:
NullReferenceException: Object reference not set to an instance of an object
UnityEditor.Scripting.ScriptCompilation.EditorBuildRules.GetAllScriptAssemblies (IEnumerable`1 allSourceFiles, System.String projectDirectory, BuildFlags buildFlags, UnityEditor.Scripting.ScriptCompilation.ScriptAssemblySettings settings, UnityEditor.Scripting.ScriptCompilation.CompilationAssemblies assemblies) (at /Users/builduser/buildslave/unity/build/Editor/Mono/Scripting/ScriptCompilation/EditorBuildRules.cs:180)
UnityEditor.Scripting.ScriptCompilation.EditorCompilation.GetAllScriptAssemblies (BuildFlags buildFlags, EditorScriptCompilationOptions options,
....
and
NullReferenceException: Object reference not set to an instance of an object
TMPro.TMP_Settings.get_defaultFontAsset ()
TMPro.TextMeshProUGUI.LoadFontAsset ()
TMPro.TextMeshProUGUI.OnValidate ()
2. How we can reproduce it using the example you attached
- Have a new project
- Find the package in Asset Store (https://www.assetstore.unity3d.com/en/#!/content/84126)
- Import
- It asks for script updater to be run. Confirm.
---> Errors appear in Console at import completion
Note that there was only the second error in 5.6.0p1. And there are no errors in 5.5.2p2.
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
This is a duplicate of issue #902710