Search Issue Tracker
Active
Votes
2
Found in
2021.2.0a20
2021.3
2021.3.2f1
2022.1
2022.2
Issue ID
1429664
Regression
Yes
"Unable to find player assembly Testrunner.dll" warning appears in the Console after building Standalone
Reproduction steps:
1. Open the attached "1429664.zip" project
2. Build for Windows, Mac, Linux Standalone
3. Observe the Console
Expected result: There are no warning messages
Actual result: "Unable to find player assembly Testrunner.dll" warning message appears
Reproducible with: 2021.2.0a20, 2021.3.5f1, 2022.1.6f1, 2022.2.0a17
Not reproducible with: 2019.4.40f1, 2020.3.36f1, 2021.2.0a19
Tested and reproduced with: Windows 10
Note: Couldn't reproduce on a newly created project
First few lines of the Warning:
Unable to find player assembly: C:\Users\<project path>\Temp\StagingArea\Data\Managed\UnityEngine.TestRunner.dll
0x00007ff6baaeb5cd (Unity) StackWalker::GetCurrentCallstack
0x00007ff6baaf2329 (Unity) StackWalker::ShowCallstack
0x00007ff6bba59713 (Unity) GetStacktrace
0x00007ff6bc0e314d (Unity) DebugStringToFile
0x00007ff6b9c46bd2 (Unity) DebugLogHandler_CUSTOM_Internal_Log
0x00000262fdb26f03 (Mono JIT Code) (wrapper managed-to-native)
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