Search Issue Tracker

Fixed in 1.1.16

Votes

4

Found in [Package]

0.2.2-preview.6

Issue ID

1210156

Regression

Yes

[Jobs][DOTS] Building empty project with Jobs results in "Unable to find player assembly" errors

Package: Test-Framework

-

Reproduction steps:
1. Create a New Project
2. Import the "Jobs" package
3. Build a Standalone build
4. See Console

Expected Result: No errors
Actual Result: "Unable to find player assembly: '...UnityEngine.TestRunner.dll'/'Unity.PerformanceTesting.dll'" errors

Reproduced with: 2020.1.0a19, 2019.3.0f5, 2019.2.18f1
Did not reproduce on: 2018.4.15f1, 2017.4.36f1 (No Packman)

Comments (4)

  1. Sora255

    May 31, 2021 12:59

    Unable to find player assembly: C:\UnityProject\Inferno\Temp\StagingArea\Data\Managed\UnityEngine.TestRunner.dll
    0x00007ff73778726c (Unity) StackWalker::GetCurrentCallstack

    Test Framework 1.1.26 - May 26, 2021
    Burst 1.5.4 - May 17, 2021
    Jobs 0.8.0-preview.23 - January 22, 2021

    Unity 2020.3.9f1

  2. Bartolomeus755

    Jan 26, 2021 13:38

    It's not fixed with 1.1.16. I have this warning also with 1.1.22 and Unity 2020.2.2f1.

  3. Thygrrr

    Dec 26, 2020 00:33

    Definitely occurs in Unity 2020.1.17f1 and 2020.2.1f1

  4. lclemens

    Aug 30, 2020 17:07

    "Fixed in 1.1.16"?? I"m not so sure...

    I have Test Framework version 1.1.16 with version 2020.1.2. Every build produces:

    Unable to find player assembly: C:\Code\MyProject\Temp\StagingArea\Data\Managed\UnityEngine.TestRunner.dll

    Unable to find player assembly: C:\Code\MyProject\Temp\StagingArea\Data\Managed\Unity.PerformanceTesting.dll

    I do have Burst AOT enabled (Enable Burst Compilation and Enable Optimisations (SIC)) since I'm using the burst compiler.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.