Search Issue Tracker
By Design
Votes
0
Found in
5.0.0f4
Issue ID
678565
Regression
No
WebGL throws Uncaught SyntaxError: Unexpected number
To reproduce:
1. Open attached project
2. Build and run WebGl build
3. "Uncaught SyntaxError: Unexpected number." error thrown
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
- Highlighter.Highlight does not find window when using class name as window title
- Highlighter.Highlight highlights a different component when multiple components have the same property path
- Highlighter.Highlight does not find elements in an array or list when the array or list is collapsed
- [URP][NRP] RenderPass, BeginSubPass, and EndRenderPass errors are thrown when Native RenderPass is enabled
- D3D11 swapchain error pop-up appears and the Editor shuts down when Generating Lighting with Probe Volumes present
AccentDave
Apr 05, 2016 23:20
This is a deal-breaker for us. We have to find another platform other than Unity. It happens on Chrome, not Firefox. IE won't touch it. It seems, looking at the console, that the headers are somehow included in the body of the HTML and it's choking on that (???)
Please fix this
Woody4618
Oct 09, 2015 12:16
Happens for me too. Only in Chrome though
w34edrtfg
Aug 05, 2015 18:24
I can reproduce this error using only 2 simple scripts. If someone provides me an email to send the project, i will send it (179kb..)
sballew7
Apr 16, 2015 23:08
Is there any way to know that is the cause? Anything more specific than "Unexpected number"?
Tautvydas-Zilys
Apr 16, 2015 17:57
This particular issue description is very confusing. In this case, the exception was being thrown because C# code was accessing threads, which are not supported by WebGL.
sballew7
Apr 15, 2015 23:35
Running into this same thing, and I haven't found anything on it except this issue. Why was this resolved by design?
pfc
Mar 28, 2015 23:16
How can a thrown syntax error be by design? What can be done about it?