Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.4
2017.4.30f1
Issue ID
1173024
Regression
No
[UWP] Building project to UWP fails with errors when simple UnityScript files are attached
How to reproduce:
1. Open attached Unity project
2. Create empty scene
3. Build to UWP
Result: build fails with errors.
Workarounds:
Renaming "ShipAI.js" to "AI.js"
Changing line in Manifest.js from "var aiType:eAI" to "var aiType:int"
Reproduced with: 2017.4.31f1.
Note: This issue is not reproducible on Unity 2018.1 and later because JavaScript is not supported from 2018.1 version.
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
- 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
Resolution Note:
The project is targeting .NET 4.6 API compatibility level, which never supported UnityScript. Switching to .NET 2.0 API compatibility level makes the errors go away.