Search Issue Tracker
Fixed in 2018.3.X
Votes
0
Found in
2018.2.0a1
2018.2.2f1
Issue ID
1067185
Regression
Yes
JavaScript files under WebGLTemplates folder are being compiled as UnityScript after modifying them
How to reproduce:
1. Open the attached "TestFor1067185.zip" project
2. Go to Assets -> WebGLTemplates -> TestTemplate
3. Modify testScript.js file and save it
4. Observe the compilation errors in the Console window
Expected result: JavaScript files under WebGLTemplates folder are ignored
Actual result: JavaScript files under WebGLTemplates folder being compiled as UnityScript
Reproducible with: 2018.2.0a1, 2018.2.2f1, 2018.3.0a8
Not reproducible with: 2017.1.5f1, 2017.2.3p3, 2017.4.9f1, 2018.1.9f1
Update: fixed in 2018.3.0a11
Comments (3)
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
- Play Mode Scenario selection/highlight is too long and out of its bounds when the Play Mode Scenario window is opened after maximizing
- Duplicated groups and incorrect grouping in UI Builder when using UxmlElementAttribute: libraryPath
- Asset name is not shown in the Undo History window when a sprite is modified
- Moving a Tab to a floating window fails when floating windows are docked next to each other
- Crash on UNITY_FT_Render_Glyph_Internal when Generating Font Atlas in the Font Asset Creator Window
pedro_unity228
Dec 14, 2018 21:33
The workaround I found was to rename my WebGLTemplate files from .js to .javascript and fixing the references from index.html.
Definitely not something fun to do but seems to work short-term.
pedro_unity228
Dec 14, 2018 20:47
Finally found someone else with this problem. Happy to hear it's fixed in 2018.3... Please backport to 2018.2! Is there a known workaround? It's now got me completely stuck. :-(
tonialatalo
Sep 25, 2018 18:06
Any backport of this for 2018.2, maybe in a patch release soon?
Does not really help that it's fixed in 2018.3 at this point.