Search Issue Tracker
Fixed
Fixed in 1.8.0
Votes
0
Found in [Package]
1.7.7
1.7.8
1.8.0
Issue ID
UVSB-2381
Regression
Yes
AOT stub generator ignores assemblies that reference Unity editor
h3. Steps to reproduce:
# Open the attached project which has a script graph with a single cinemachine node.
# Build and run the project.
# Examine the Player.log
h3. Results:
There are errors running the game as the method was stripped from the build.
{code:java}
Failed to define GetMember#e5b4c...:
System.MissingMemberException: Member 'Cinemachine.Cinemachine3rdPersonAim.AimDistance' not found.{code}
h3. Expected Results:
We generate the AOT stub and no error occurs.
Here are some recommendations as suggested per Rohit:
# Generate AOT Stubs for all nodes used in all graphs, regardless of their editor / runtime status. This means that yes: Users might be able to put editor only nodes in their graphs that will break their builds, but if:
# (If this is possible) We add good error messaging for when a node causes a bad stub. This would let users remove nodes that cause errors from their graphs
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
Add comment