Closed ueman closed 5 months ago
Re: https://github.com/getsentry/sentry-dart/pull/2033#issuecomment-2107057981
@ueman Just for clarification, I based the exception on the tests that were there:
Is this then also incorrect, as it also puts the stacktrace string into
message
andstacktrace
properties? The order of message/details is also different in the ctor than in the test sample declarations.
I think I messed up when implementing that, since I've never seen a stacktrace in the message property, but I've seen plenty stacktraces in the details property
Any easy way to provoke a PlatformException to have one more example?
I can take a look at what we observe in production and add some more examples
I can't reopen #2001, so here's a new issue since #2001 isn't actually fixed in #2033.
The issue is that the exception seen below has the stacktrace in the details field, but the details field is not parse. In practice, I never see the stacktrace in the message field, however the message field is correctly parsed if present.
It's probably a good idea to let
details
take precedence overmessage
.Platform
Flutter Mobile
Obfuscation
Disabled
Debug Info
Disabled
Doctor
Version
7.18.0
Steps to Reproduce
Catch the PlatformException mentioned below
Expected Result
The exception is correctly parsed.
Actual Result
which corresponds to the following Dart code:
Are you willing to submit a PR?
None