Search Issue Tracker
Fixed in 2020.2.X
Votes
0
Found in
2020.2.0a20
Issue ID
1267366
Regression
Yes
[Build Pipeline] Player cannot access class that is part of the project
I'm using https://github.com/Unity-Technologies/SpaceshipDemo to perform tests on a Mac, 2020.2a19 successfully runs a player build
After an update landed to trunk, I'm seeing an issue with the player build unable to find a class that's part of the project, failing to continue with the execution. Works fine in the editor
Manager of type 'GameplayIngredients.FullScreenFadeManager' could not be accessed. Check the excludedManagers list in your GameplayIngredientsSettings configuration file.
UnityEngine.StackTraceUtility:ExtractStackTrace () (at /Volumes/Users/aet/src/unity/unity/Runtime/Export/Scripting/StackTrace.cs:37)
UnityEngine.DebugLogHandler:LogFormat (UnityEngine.LogType,UnityEngine.Object,string,object[])
UnityEngine.Logger:Log (UnityEngine.LogType,object)
UnityEngine.Debug:LogError (object)
GameplayIngredients.Manager:Get<GameplayIngredients.FullScreenFadeManager> () (at /Volumes/Users/aet/src/unity/projects/SpaceshipDemo/LocalPackages/net.peeweek.gameplay-ingredients/Runtime/Managers/Manager.cs:19)
GameplayIngredients.Actions.FullScreenFadeAction:Execute (UnityEngine.GameObject) (at /Volumes/Users/aet/src/unity/projects/SpaceshipDemo/LocalPackages/net.peeweek.gameplay-ingredients/Runtime/LevelScripting/Actions/FullScreenFadeAction.cs:21)
GameplayIngredients.Callable:Call (GameplayIngredients.Callable[],UnityEngine.GameObject) (at /Volumes/Users/aet/src/unity/projects/SpaceshipDemo/LocalPackages/net.peeweek.gameplay-ingredients/Runtime/LevelScripting/Callable.cs:34)
GameplayIngredients.Events.OnStartEvent:Start () (at /Volumes/Users/aet/src/unity/projects/SpaceshipDemo/LocalPackages/net.peeweek.gameplay-ingredients/Runtime/LevelScripting/Events/OnStartEvent.cs:13)
Tested on 2020.2.0a20
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Add comment