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)
-
slikeytre
Jan 29, 2020 19:56
Having same issue on 2019.3.0f6
-
hoshos
Jan 27, 2020 15:36
Same problem in 2019.3.0f5.
Assertion failed on expression: 'gForceReimports->empty()'
UnityEditorInternal.InternalEditorUtility:ProjectWindowDrag(HierarchyProperty, Boolean)
UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr)I get this with the function of PrefabUtility.
PrefabUtility.SaveAsPrefabAssetAndConnect(target, prefabPath, InteractionMode.AutomatedAction, out success);If this happens, the sub-assets will not be saved correctly and the links will be broken.
I want a quick response. -
ByteStormGmbH
Jan 09, 2020 14:12
I have the same issue with 2019.3.0f1 :
Assertion failed on expression: 'gForceReimports->empty()'
UnityEditorInternal.InternalEditorUtility:ProjectWindowDrag(HierarchyProperty, Boolean)
UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr) -
aRSENIY-sICHEV
Dec 18, 2019 08:44
Having the same issue on 2019.3.0f1
-
Whitepot
Dec 12, 2019 16:47
I can't edit my previous comment, but this issue was resolved by
- going to tools > Doozy > refresh for Doozy UI
- completely removing FMOD Unity Integration 2.00.06Both are plugins that are installed in a 'base' unity project which we clone from when making a new project repository. The FMOD plugin seems to be biggest headache at the minute, they recommend downgrading to 2.00.05 for now.
Threads:
https://qa.fmod.com/t/downgrade-to-previous-fmod-version/15269
https://qa.fmod.com/t/lag-every-5-seconds/15241/4 -
Whitepot
Dec 11, 2019 11:47
Same issue here in 2019.3.0f1 Personal - project is based on a new Unity Lightweight Render Pipeline project and includes Unity IAP, Ads, Google Play Services, etc.
Anytime you try to make a new root folder in 'Assets', the following error appears in the console and no folder is made:
` Assertion failed on expression: 'gForceReimports->empty()'
UnityEditor.AssetDatabase:ImportAsset(String)
` FMODUnity.EventManager:CopyToStreamingAssets() (at Assets/Plugins/FMOD/src/Editor/EventManager.cs:534)
` FMODUnity.EventManager:RefreshBanks() (at Assets/Plugins/FMOD/src/Editor/EventManager.cs:37)
` FMODUnity.EventManager:Update() (at Assets/Plugins/FMOD/src/Editor/EventManager.cs:670)
` UnityEditor.EditorApplication:Internal_CallUpdateFunctions() -
RobertVerdes
Nov 30, 2019 12:17
Fixed for me by upgrading project (from Unity 2019.3.0b10) to Unity 2019.3.0f1.
-
Tazoru
Nov 24, 2019 00:28
Still occur on 2019.3.0b12 (project upgraded from previous 2019.3 versions)
-
Danief_
Nov 23, 2019 20:23
Same problem with 2020.1.0a11 Personal.
-
Max_Bol
Nov 22, 2019 02:11
Also have this error on Unity 2019.3.0b11 Personal.
The full Error message is :
Assertion failed on expression: 'gForceReimports->empty()'
UnityEditor.AssetDatabase:Refresh()
SyntaxTree.VisualStudio.Unity.Bridge.<>c:<Refresh>b__11_0()
SyntaxTree.VisualStudio.Unity.Bridge.<>c__DisplayClass40_0:<RunOnceOnUpdate>b__0()
UnityEditor.EditorApplication:Internal_CallUpdateFunctions()
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