Search Issue Tracker
Fixed
Votes
0
Found in
2020.2.0a17
2020.2.0b3
Issue ID
1277881
Regression
Yes
IL2CPP builds fail when using Mirror networking package
Reproduction steps:
1. Open the attached project ("case_1277881-IL2CPP-Mirror-build.zip")
2. Try making Standalone IL2CPP build.
Expected result: Build succeeds
Actual result: Build fails with "il2cpp.exe didn't catch exception: Unity.IL2CPP.AggregateErrorInformationAlreadyProcessedException" error
Reproducible with: 2020.2.0a17, 2020.2.0b3
Not reproducible with: 2018.4.27f1, 2019.4.10f1, 2020.1.6f1, 2020.2.0a16
Notes:
1. The issue does not reproduce when building with Mono backend
2. Mirror is based on Unity's abandoned UNET Networking system, and it can be found on Asset Store: https://assetstore.unity.com/packages/tools/network/mirror-129321
Comments (1)
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
- Texture generator reference image fails despite valid size
- Agent mode can enter infinite execution loop
- AI Gateway responses contain duplicated sentences
- Texture 2D asset is created when promoting a generated Cubemap to a new asset
- Unable to copy multiple paragraphs from Assistant responses
larus
Dec 15, 2020 21:04
The bug is actually in Mirror weaver code, but it's also in UNet weaver. This has been fixed in com.unity.multiplayer-hlapi package, version 1.0.8. Similar fix likely also works for Mirror. It was in UNetWeaver.cs during the cecil ResolveMethod calls, for the log functions Debug.LogWarning and Debug.LogError. Issue was the function signatures changed in 2020.2 and the weaver generated invalid IL code as a result.