Full stack information not properly capturing for ios. about bugsnag-unity

[clr182]

Hi @rakshithshettyhcl

Apologies about the delay in response time. We are currently investigating this and will let you know once we have more information.

[clr182]

Hi @rakshithshettyhcl

Apologies about the delay in response time.

As we do not yet have the mechanisms in place to symbolicate IL2CPP framework code this does look like expected behaviour for the iOS exception. We do have an item on our backlog aimed at solving this. I don't have a firm ETA but i'll be sure to update you once we have more information to share.
We are still unsure why your dashboard seems to be missing the top most stack frame.

I have created a reproduction example application and unfortunately I have been unable to reproduce the missing first stack trace between the information sent to BugSnag and the XCode debugger terminal. Both my dashboard and XCode terminal result in the same number of stack trace frames.

Additionally, creating an infinite while loop has not reacted in a crash to the application using the code that you have provided. Is this the same code you are using to test on your end or is this a cut down example for the purposes of reproduction? If not then could you please provide us with the example code.

It's possible that this way of crashing the application has resulted in this issue. Any additional context in this would help us to investigate further. I should also ask, are you perhaps performing any manual stacktrace manipulation for events a callback method that may be the cause?