Skip to content
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

Closed
Karlie-777 opened this issue Sep 29, 2021 · 5 comments
Closed

[BUG] enableUnhandledPromiseRejectionTracking shows no error trace #1679

Karlie-777 opened this issue Sep 29, 2021 · 5 comments
Assignees
Milestone

Comments

@Karlie-777
Copy link
Contributor

when parsing onunhandledrejection error event, error.reason.toString() is passed to Exception.CreateAutoException() function and the error.reason.toString() will expose no detailed trace stack . Instead error.reason.stack.toString() should be used to enable full trace tracking.

@Karlie-777 Karlie-777 pinned this issue Sep 29, 2021
@Karlie-777 Karlie-777 unpinned this issue Sep 29, 2021
@Karlie-777
Copy link
Contributor Author

linked to issue: #1675

@Karlie-777 Karlie-777 added the bug label Sep 29, 2021
@Karlie-777 Karlie-777 self-assigned this Sep 30, 2021
@nika1001
Copy link

nika1001 commented Sep 5, 2022

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.
Rejected promise is correctly logged but with no stack information. Inspection of PromiseRejectionEvent shows that stack is under reason prop but is not parsed by _getStackFromErrorObj:
image

@Karlie-777
Copy link
Contributor Author

@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.

@MSNev MSNev added this to the 2.8.8 milestone Sep 12, 2022
@MSNev MSNev added the fixed - waiting release PR Committed and waiting deployment label Sep 13, 2022
@MSNev
Copy link
Collaborator

MSNev commented Sep 15, 2022

@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.
The full nightly release night build is nightly-2209-02

@github-actions
Copy link

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 11, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants