-
Notifications
You must be signed in to change notification settings - Fork 21
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
Stack Trace is wrong in release mode (Flutter/Android) #122
Comments
fordcars
changed the title
Stack Trace is wrong in release mode (Android)
Stack Trace is wrong in release mode (Flutter/Android)
Nov 28, 2022
We have a similar problem. We use
I also wanted to add that the same problem affects both platforms: android and ios.
|
To understand whether this is a bug in this package or in SDK, do you also get wrong stack traces if you use |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Calling
Trace.current()
in debug works perfectly. However, callingTrace.current()
in release mode yields a different stack which is definitely wrong (this code path is impossible). Most, if not all stack traces I get in release mode are like this (where one or two function calls are wrong).Debug stack trace, showing correct GlobalChannelProxyService.createChannel call:
Release stack trace, showing impossible GameServiceProxy.executePlace call:
Please note GameServiceProxy.executePlace is never even called in the app. It is, however, an async function, which may be related. If I comment the GameServiceProxy.executePlace function, the release stack trace will be different, but still wrong:
Release stack trace with commented GameServiceProxy.executePlace function:
Please note the SelfUserProxyService.user, which is also an impossible path. It looks like 2 stack traces got mangled in this case.
The text was updated successfully, but these errors were encountered: