You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Calling Trace.current() in debug works perfectly. However, calling Trace.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).
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:
To understand whether this is a bug in this package or in SDK, do you also get wrong stack traces if you use StackTrace.current instead of Trace.current?
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: