Search Issue Tracker
Not Reproducible
Votes
3
Found in
2017.4.13f1
Issue ID
1093054
Regression
No
[UWP][.NET] Building solution in Visual Studio fails on AssemblyConverter when project contains Unity IAP 1.20.1
How to reproduce:
1. Open the attached project that contains Unity IAP 1.20.1
2. In Build Settings, make sure that Target Platform is UWP
3. In Player Settings, make sure that the Scripting Backend is set to .NET
4. Build the project
5. In the Console window, observe that the build was successful, but with Reference rewriter errors
6. Open the build solution file in Visual Studio
7. Build the solution
Expected result: The solution is built successfully. (Also, step 4 does not result in Console errors.)
Actual result: Building the solution fails. (Also, there are Console errors as mentioned in step 5.)
Reproducible with - 2017.4.14f1, 2018.2.14f1, 2018.3.0b8
Notes:
- Not tested on 2019.1, since the issue occurs only when Scripting Backend is .NET (and this Scripting Backend is deprecated in 2019.1).
- The issue does not occur when IAP version is 1.18 or 1.20.0. It was only reproducible on the latest IAP version at the time - 1.20.1.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Add comment