A lot of my players are getting the same error. We collect the JavaScript logs and it shows up as "abort(153) at jsStackTrace" but the since the stack trace is minified, I can't really get any information about where in the code something goes wrong from it.
I've had a look at [this talk from Unite Europe 2016][1], where a dev explains that you can create a symbol map that can be used to decipher the stack trace. (Link goes exactly to the part where he talks about it)
He talks about having to pass an argument in order for the symbol map to be emitted, but according to [this answers post][2], Unity 5.4 and upwards takes care of that internally.
So here comes the part that I'm struggling with:
**What exactly is a symbol map and how do I use it to read the jsStackTrace error?**
Unfortunately, the talk I linked to just says that you can use the map to decipher the StackTrace, but doesn't mention how, and I've been unable to find anything else on the subject.
As far as I know, I could build with Full Exception Support in order to get readable logs, but that would drastically increase file size and have an impact on performance, which is why I'd prefer to find another solution.
[1]: https://youtu.be/VR6jFgAVCNI?t=23m37s
[2]: http://answers.unity3d.com/questions/1147408/can-unity-export-the-emscripten-symbols-map-on-web.html
↧