Search Issue Tracker
Won't Fix
Votes
0
Found in
2019.1.0b8
2019.1.0b9
Issue ID
1140993
Regression
Yes
"InvalidOperationException: Cannot find CustomScriptAssembly" thrown after deleting folder from MixedRealityToolkit
How to reproduce:
1. Open the attached "InvalidOperationExceptionBug.zip" project
2. Delete "Assets\MixedRealityToolkit\Utilities\BuildAndDeploy" folder
3. Observe the Console
-- Multiple "InvalidOperationException: Cannot find CustomScriptAssembly with name <...>" errors appear AND recompilation process does not end
Reproducible with - 2019.1.0b8, 2019.1.0b9
Not reproducible with - 2018.3.11f1, 2019.1.0b7, 2019.2.0a10
Note: The issue is not present after reopening the project.
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (2019.1.X):
MRTK is developed/supported by Microsoft and not handled by the XR team. Won't fix.