Search Issue Tracker
By Design
Votes
0
Found in [Package]
1.7.3
1.7.6
Issue ID
UVSB-1661
Regression
No
Visual Scripting "AotStubs.cs" Script is not generated when building for iOS/WebGL in batch mode
Reproduction steps:
1. Download the "1077231_MyProject.zip" project
2. Build the project using the 'Builder.MyBuild' method via command line (\{EDITOR_PATH} -projectPath \{PROJECT_PATH} -batchmode -executeMethod Builder.MyBuild -quit)
3. Wait till it's finished and inspect the project's Assets folder
Expected result: "Unity.VisualScripting.Generated" folder was generated and the "AotStubs" Script can be found inside
Actual result: "Unity.VisualScripting.Generated" folder was not generated
Reproducible with: 1.7.3 (2021.1.15f1, 2021.2.0b4, 2022.1.0a4)
Could not test with: below 2021.1 (Visual Scripting not supported)
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
- The Scene View becomes gray and "NullReferenceException" errors are thrown when attaching the Unity Editor process to RenderDoc
- Memory usage rapidly rises when changing colors in the color wheel
- Physically Based Sky's Horizon and Zenith Tint Color Selection Bars don't have immediate access to color pickers
- EmptyAdditionalLightShadowmapTexture leaks from memory when URP quality level is changed using QualitySettings.SetQualityLevel
- Referenced ScriptableObject field does not get updated and cannot be set to "None" when there are no Objects of that type
Resolution Note:
from @yuri
The AotStubs files are created during the build process and deleted afterward. But only if the Visual Scripting is initialized.
It is possible to check if VS is initialized by looking for the folder "Unity.VisualScripting.Generated".
If you have VS initialized, a scene with a gameobject that has a graph attached, you should be able to build a working project on batch mode using the latest Visual Scripting version.
Use the attach project to run your tests.WorkingProject.zip