-
-
Notifications
You must be signed in to change notification settings - Fork 220
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
PlatformException on Android isn't correctly parsed #2041
Comments
Re: #2033 (comment)
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
The text was updated successfully, but these errors were encountered: