-
-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash reports on Mac player with Mono runtime do not include file path or line numbers #1763
Comments
That's odd for sure. Mono should work OOTB with whatever it is that Unity provides us. We'll have to check if that is something new with Unity 6. |
Yeah, it's odd. As I said it does work on a Windows build built on a Windows machine, but not on a Mac build built on a Mac machine. |
I'm looking into this as part of #1775 |
Interestingly enough the stacktraces differ out-of-the-box between an error captured in the
vs a
|
Environment
How do you use Sentry?
Sentry SaaS (sentry.io)
Which version of the SDK?
sentry-unity 2.1.3
How did you install the package? (Git-URL, Assetstore)
Git
Which version of Unity?
6000.0.14f1
Is this happening in Unity (editor) or on a player like Android, iOS, Windows?
Player
Steps to Reproduce
Any crash.
Expected Result
Sentry shows file name and line numbers.
Actual Result
This is the full "Raw Stack Trace" that appears in Sentry.
No file or line numbers appear in the symbolicated trace UI.
I am having a similar issue on Windows players (built on Windows), where file and line numbers do appear, but they use Windows-style paths and Sentry cannot associate the source code with them. #1764 Perhaps there is some connection between the two.
The text was updated successfully, but these errors were encountered: