Search Issue Tracker
Fixed
Fixed in 1.7.6
Votes
0
Found in [Package]
1.7.2
1.7.5
Issue ID
UVSB-1649
Regression
No
Visual Scripting with IL2CPP Build built using Batch Mode throws ExecutionEngineException
Steps to reproduce:
1. Download and open the project "VisualScriptingIL2CPPTest.zip"
2. Open Build Settings (File > Build Settings...)
3. Add Assets/SampleScene.unity to Scenes In Build
4. Click on Build And Run
5. After the Build is complete, open the Player.log file found in %USERPROFILE%\\AppData\\LocalLow\\<studioname>\\ScriptingTest
6. Notice that no exceptions are thrown
7. Open the Build.bat file located in the root folder of the project
8. Edit the path within the "" to point to the same Unity Editor in which the project was opened in
9. Save and run the Build.bat file
10. Run the resulting Build.exe file located in the Build directory
11. Open the Player.log file
Expected result: No exceptions are thrown
Actual result: ExecutionEngineException: Attempting to call method 'Unity.VisualScripting.InstanceFunctionInvoker is thrown
Reproducible with: 1.7.2 (2021.1.15f1, 2021.2.0b5)
Could not test with: Bolt 1.4.15 (2018.4.36f1, 2019.4.29f1, 2020.3.14f1) (Multiple Package/Assembly errors)
Note:
Issue not reproducible with Mono Scripting Backend
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
- “[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
Resolution Note (fix version 1.7.6):
This issue was fixed with Version 1.7.6 that is already released