Search Issue Tracker
Active
Votes
2
Found in [Package]
2.2.1
Issue ID
1417456
Regression
No
"Unity.Tutorials.Core.Editor.BuildStartedCriterion" class instantiation-related warning is thrown on Player build
How to reproduce:
1. Open a new 3D project
2. Install the "Tutorial Framework" Package in the "Package Manager"
3. Build a Player
Expected result: Player is successfully built without any errors or warnings
Actual result: Two instances of "Unity.Tutorials.Core.Editor.BuildStartedCriterion must be instantiated using the ScriptableObject.CreateInstance method instead of new BuildStartedCriterion." warnings are thrown in the Console log
Reproducible with: 2.2.1 (2019.4.37f1, 2020.3.33f1, 2021.3.0f1, 2022.1.0b15, 2022.2.0a10)
Comments (1)
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
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
qwv
Nov 18, 2024 08:01
Still happening in Unity 6 with Tutorial Framework 4.0.3