Search Issue Tracker
Not Reproducible
Votes
12
Found in
2019.3.0b2
2019.3.0b3
2020.1.0a1
Issue ID
1184079
Regression
Yes
Assertion failed on expression: 'gForceReimports->empty()' is thrown when adding scripts to inspector
How to reproduce:
1. Create and open a new Universal RP template project
2. Observe the console window
Expected result: no errors are thrown
Actual result: Assertion failed on expression: 'gForceReimports->empty()' is thrown
Reproducible with: 2019.3.0b2, 2019.3.0b4, 2020.1.0a5 (7.0.1)
Not reproducible with: 2018.4.9f1 (4.1.0), 2019.2.7f1 (6.9.0), 2019.3.0b1 (7.0.1)
Could not test with: 2017.4.32f1 (Template not available)
-
codebreakerru
Jun 26, 2020 00:11
same issue June 26 2020
-
ciathyza
Jun 18, 2020 11:04
Same issue still occurring with Unity 2019.4.0f1 HDRP.
-
Hazneliel
Jun 15, 2020 05:04
Observing this issue on 2019.4.0f1
-
DrummerB
May 30, 2020 18:09
Still happening with Unitz 2020.1.0b9 and HDRP 8.0.1
-
JoniD89
May 08, 2020 10:37
Same issue. Version 2019.3.6f1 occurred when added a script component to a prefab creating a new script.
-
SunnyValleyStudio
May 07, 2020 11:23
Same issue 2019,3,10f1
-
Christoo25
May 06, 2020 20:37
I have the same issue with Unity 2019.3.12f1
-
polyphonic13
Apr 25, 2020 17:49
I'm having the issue in 2019.3.2f1.
-
polysoft3D
Apr 22, 2020 23:11
same Unity 2019.3.0b9
-
Andrew-Carvalho
Apr 21, 2020 16:50
Also getting this, also using the FMOD plugin (2.00.08).
I don't mind editing the plugin to fix the issue but the error is vague enough that I wouldn't know where to start looking without spending time investigating.
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
Resolution Note:
Looks like it is fixed in newer versions of Unity, at least we were not able to reproduce on latest 2019.3.x builds