Any ideas how to get a decent stack trace?
This old thread has some suggestions, but none of these flags seem to work today.
We solved it by injecting custom build step into Unity build pipeline. More precisely, we replaced [UnityEditorPath]/Editor/Data/il2cpp/il2cpp.exe with our own exe that calls the real il2cpp.exe by editing its arguments. So calling il2cpp.exe without –enable-stacktrace and with –emit-null-checks and –enable-array-bounds-check arguments are settings that worked for us.
For the first few weeks after the initial release, the biggest issues were that we didn’t find a good way to decipher the minified stack traces we got in our exception reports. Fortunately, we found the solution later by passing the –emit-symbol-map parameter to the Emscripten compiler.