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
- APV data is sometimes incorrectly loaded from multiple baking sets when loading a scene
- GC Alloc spikes occur when calling UnityEngine.Resolution and UnityEngine.RefreshRate with Equals() and GetHashCode()
- Type error is thrown when a new ComputeShader is instantiated after destroying previous ComputeShader
- APV data becomes incorrect when reselecting the currently active Baking Set
- Launch screen image exceeds the screen bounds on IPad when building for iOS
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.