MLAPI after setting up game for Unit Tests

[benlabbeus]

I'm attempting to setup a PlayMode Unit Test using Test Runner.

UPDATE: Downgrading to Unity 2019 resolves.

Describe the bug
Field `MLAPI.NetworkManager:__ntable' is inaccessible from a Unity Assembly Definition

To Reproduce
In a simple scene using MLAPI with a NetworkManager and a NetworkObject -

1. Open Test Runner
2. Create a PlayMode Test Assembly Folder
3. Create Test Script in current Folder
4. From the Project window, Create a Assembly Definition, name it "Scripts"
5. On the new "Scripts" Assembly definition Add com,unity.multiplayer.mlapi.runtime as a Assembly Definition Reference
6. Run, you'll then get the error -
   FieldAccessException: Field MLAPI.NetworkManager:__ntable' is inaccessible from method xxxx.xxxx:.cctor ()'

Rethrow as TypeInitializationException: The type initializer for 'xxxx.xxxx' threw an exception.

Deleting the "Scripts" Assembly Definition returns things to working order.

Environment (please complete the following information):

• OS: Windows 10
• Unity Version: 2020.3.2.f1
• MLAPI Version: 0.1.0
• MLAPI Commit:

[0xFA11]

I'm not entirely clear what the issue is there, you should NOT use/access/reference NetworkManager.__ntable at all.

Do you mind sharing your test script or a simple project attached that reproduces this issue?

[benlabbeus]

Trying to use MLAPI at all in Unity 2020.3.2.f1 when you have an Assembly Reference Definition in your scripts folder causes this break.

It will break on this hello world app -
https://docs-multiplayer.unity3d.com/docs/tutorials/helloworldintro

If you remove the Assembly Reference Definition everything works. Or downgrading to v2019 and keeping the Assembly Reference Definition also works.

[0xFA11]

@blabz2007 — so you do not have a script file under that newly created asmdef at all, right?
also, do you mind sharing the full editor logs with me?

[benlabbeus]

This is the setup -

[0xFA11]

@blabz2007
can you share HelloWorld (or HelloWorldPlayer?) script as well?

[benlabbeus]

HelloWorldManager.zip

[0xFA11]

@blabz2007 — I'm still not able to reproduce this issue on 2020.3.2f1 with MLAPI 0.1.0 release.
Please can you send the full project zipped so that I can have a better look and understand what's the problem? :)

[benlabbeus]

Np! Thank you for taking the time to look into it!
MLAPIBug.zip

[0xFA11]

@blabz2007 — I got the error!
For some reason, UNITY_2020_2_OR_NEWER macro was unset/false in the project, which shouldn't be because we're on 2020.3.2f1.
I deleted Library, Temp, obj, sln and csproj files then reopened Unity to let it reimport all the things, issue gone!
So, maybe there were some artifacts from 2019.4 I assume? were you upgrading from 2019.4?
If not, do you mind quickly reproducing this issue from scratch on an empty 2020.3.2f1 project?
(I feel like it might be quite a work for you but it's really strange so we need your help 🙂 )

[jmguillemette]

has this fix been released yet? im getting the same issue and I downloaded the library just yesterday.