Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.3.0a1
2018.3.0f2
2019.1.0a1
Issue ID
1140714
Regression
No
UI Canvas renders invisible when project is built
Steps to reproduce:
1. Open User-supplied project ("Pixel Fights.zip")
2. In the File -> Build Settings check all the Scenes to be built
3. Build the game
Expected: The Canvas, which is visible in the Editor is also rendered in the built project
Actual: The Canvas is invisible in the built version
Reproduced in: 2018.3.10f1, 2019.1.0a10
Not reproduced in: 2017.4.24f1*, 2019.2.0a9*
not tested due to instant crashing upon launch (stack trace in edit)
**not tested due to errors preventing the building of the project
Note: the buttons are actually present and functional, you can enter the next scene by clicking where they are supposed to be
Switching to Screen Space - Camera and World Space Canvas Render Modes seem to disable the canvas in the Editor
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.2.X):
Low priority defect for the moment. This bug is unlikely to be fixed in the near future.