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
- Addressables Report window UI is broken when opening via Build > New Build > Default Build Script
 - Addressables Profiles window UI break when creating a new Variable with a long name
 - No character limit when renaming Profile in Addressables Profile window, allowing excessively long names
 - Blurry, low quality Active Profile icon used in Addressables Profiles window
 - Tree Asset Preview window is not updated after assigning a new Material
 
Resolution Note (fix version 1.7.6):
This issue was fixed with Version 1.7.6 that is already released