Search Issue Tracker
By Design
Votes
0
Found in
2018.3.0a1
2019.1.0a1
2019.1.0b4
2019.2.0a1
Issue ID
1131514
Regression
No
[IL2CPP] Failing to connect to server using Microsoft.AspNet.SignalR.Client
Steps to reproduce:
1. Download 1131514_repro.zip
2. Build a Standalone player with IL2CPP back end
Expected results: IL2CPP player connects to the server
Actual results: IL2CPP player fails to connect to the server
Reproduced with: 2019.2.0a8, 2019.1.0b5, 2018.3.8f1
Note:
-Not reproducible with mono backend
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Frame Debugger is not disabled when switching Scenes if the Frame Debugger window is not open during the transition
- Standalone Profiler Targets another Project if a Standalone Profiler was launched in it before when switching between Edit or Play Mode Targets
- Crash on ForwardRenderLoopJob when opening a specific project
- [Android] Memory leak and eventual crash on Snapdragon 8 Gen 1+ devices when a Clear Pass is executed after Framebuffer Fetch
- PhysicsRaycaster ray length is incorrect when casting from rotated Camera
Resolution Note:
The SignalR client assembly does not work well with managed code stripping. It possible to prevent the SignalR assembly from being stripped by adding the following link.xml file to the Assets directory of this project:
<linker>
<assembly fullname="Microsoft.AspNet.SignalR.Client" preserve="all"/>
<assembly fullname="Newtonsoft.Json" preserve="all"/>
<assembly fullname="System.Core">
<type fullname="System.Linq.Expressions.Interpreter.LightLambda" preserve="all" />
</assembly>
</linker>
You can find more details about managed code stripping and IL2CPP here: https://docs.unity3d.com/Manual/IL2CPP-BytecodeStripping.html