-
Notifications
You must be signed in to change notification settings - Fork 237
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
[BUG] enableUnhandledPromiseRejectionTracking shows no error trace #1679
Comments
linked to issue: #1675 |
hi @Karlie-777 , is there any update on this bug please? We are also not seeing any stack trace with enableUnhandledPromiseRejectionTracking enabled, SDK version is 2.7.3. |
@nika1001 please try the latest version 2.8.5+ since we have some updates in new version. And also when full error trace is not available, error stack will be not parsed. |
@nika1001 FYI - the fix is now checked in and the automated pre-release night build has been published with #1900, so you should be able to pre-validate that this fixes your issue by simply using the "@nightly" build as the version. |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
when parsing
onunhandledrejection
error event,error.reason.toString()
is passed toException.CreateAutoException()
function and theerror.reason.toString()
will expose no detailed trace stack . Insteaderror.reason.stack.toString()
should be used to enable full trace tracking.The text was updated successfully, but these errors were encountered: