Search Issue Tracker
By Design
Votes
0
Found in
2017.2.0a3
Issue ID
919278
Regression
Yes
[WSA] Back-end automatically switches to il2cpp when importing a project with 2017.2.0a3
Steps to reproduce:
1. Create a new project with any version of Unity (except with 2017.2.0a3)
2. Switch platform to Windows Store
3. Set the back-end to .NET
4. Open the project with 2017.2.0a3
5. Observe the back-end has changed to il2cpp
Expected result: Back-end should not change
Actual result: Back-end changes
Reproduced with: 2017.2.0a3
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment