"Failure has occurred while loading a type" only on Build about restclient HOT 17 CLOSED

Hi,

I'm building for Windows (I'm currently on win10 pro version 1803).

I'm attaching the log for that build in the zip file I sent before.
output_log.txt

from restclient.

It seems that I forgot to mention my Unity version (2018.1.4f1). Sorry about that.

from restclient.

Hi @jdnichollsc, I managed to "fix" the situation (and I'm embarrassed that took me this long).

When trying to get more detail on the error that I was receiving I got to a point that mentioned a Newtonsoft.Json method that was throwing the exception. I found it strange but tried different approaches (even using the Unity version that someone created). No success with that version. However, that forced me to uninstall the official Newtonsoft.Json nuget package from NuGet for Unity.

Afterwards, and since the other Json library wasn't working, I reinstalled the official version through nuget. And everything started working afterwards. It was really strange. Within the Editor everything was always working. When building, stuff simply didn't work.

Maybe it was a cached version that allowed to work inside the Editor, or something else. Either way, after reinstalling Newtonsoft.Json after installing your library, everything started working.

Thank you so much for your patience on trying to help me figure out the problem.

from restclient.

Hello, thanks for report this issue!
What platform are you building for?

from restclient.

Also, can you share the logs please?

from restclient.

@MicBoucinha Is that version Beta, right?

from restclient.

@MicBoucinha It looks like an Unity issue https://issuetracker.unity3d.com/issues/dot-net-4-dot-6-fails-to-load-types-if-the-source-code-file-size-is-larger-than-1-dot-95mb

from restclient.

Hi @jdnichollsc, as far as I know it is not a beta version. However, I will try to update it and confirm if the issue you mention is fixed.

Thanks.

from restclient.

Hi @jdnichollsc, I managed to test the same project I sent you in 3 extra Unity versions and the issue remains, although in 2018.3.0b3 the message was different (Operation is not supported on this platform.)

I am attaching the logs for the 3 different versions (2018.1.6f1, 2018.1.9f2 and 2018.3.0b3).
output_log Unity 2018.1.9f2.txt
output_log Unity 2018.1.6f1.txt
output_log Unity 2018.3.0b3.txt

Regarding the issue that you linked, the situation I am facing seems different, because according to the reproduction steps that they mention, the problem occurs even in the Editor. In my case, inside the Editor, everything works perfectly. Only when Building the problem arises.

Thanks for the help.

from restclient.

@MicBoucinha Can you attach a demo please? I can't reproduce this issue

from restclient.

@jdnichollsc The first link of google drive I gave in the first report is for a simple project where the problem occurs (for version 2018.1.4f1). I used the same project in the other versions to generate a Build of the project and give you the logs. The link is still valid at: https://drive.google.com/open?id=1pUHzQEhPWuEpV1nAer7jUEYJKfdGuosq.

In the zip file is also the Build version (Development mode) of the same project. When pressing the 'S' key, a GET request is sent to a public API.

If you need something else, please let me know. Thank you for the help.

from restclient.

Hi @MicBoucinha,
Check this comment #35 (comment)
Can you try removing RSG.Promise_net35.dll and later rename RSG.Promise_standard.dll to RSG.Promise.dll?
Please, let me know

from restclient.

Hi @jdnichollsc,

I tried your suggestion and unfortunately the same problem occurs. What is even stranger is that now I have different error messages for the 2018.1.6f1 and 2018.3b3 versions. It should be of note, that this only occurs when building. Inside the Editor, everything works as expected.

Also, and considering that the problem might lie in the Nuget for Unity package that I'm using, which could be getting a wrong dll version, and for the RSG.Promise it was getting the .net standard version as expected, I decided to remove the library from there and import the .unitypackage that you have in the releases (and changed the name afterwards). The same problem occurs.

Here are the logs for these new 2 tests. Just like the previous logs I sent, this were made in a different machine which is basically "clean" (we only use it for data collection) to try to see if it could it be a configuration problem in my development machine.
output_log Unity 2018.1.6f1.txt
output_log Unity 2018.3b3.txt

Were you able to reproduce the problem in your end with the example I sent?

Thank you.

from restclient.

@MicBoucinha sorry man, I can't reproduce this issue in this moment because I'm using a Mac.
On the other hand, you're using beta versions of Unity, so you need to report this issue to the Unity team 👍
PD: If you want, try the RSG.Promise library directly and let me know if you can see the same error :)

from restclient.

Hi @jdnichollsc, Thanks. I will try to use RSG.Promise directly and let you know the results.

Regarding the beta versions, I only used it to verify if that issue you mentioned would be fixed at that point, since I'm not yet using the latest final version. The weird part of all of this to me is that it works perfectly fine inside the Editor.

All the best :) and thanks for your help.

from restclient.

ohhh no problem, I'm glad to know that you could solve it. there are issues that take us a long time to fix, it is normal haha 👍
Check this discussion JamesNK/Newtonsoft.Json#1440 (comment)

from restclient.

@MicBoucinha any good comment from the Unity Asset Store would be really appreciated :)

from restclient.