-
Notifications
You must be signed in to change notification settings - Fork 24.3k
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
DX bug: ExceptionsManager does not log root exception cause #16661
Comments
I am having the same issue, the app will not boot which is particularly frustrating as I was just introduced to native and the project, so I really can't even debug without a stack trace. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. If you think this issue should definitely remain open, please let us know why. Thank you for your contributions. |
Is this a bug report?
Yes (somehow) this is a developer experience bug for me but it's subjective.
Have you read the Contributing Guidelines?
Yes
Environment
I'm not using RN directly but it's plain Expo SDK 22 / CRNA
I don't think it's relevant but here are the dependencies:
Steps to Reproduce
"react-native-gallery": "^0.0.17",
Expected Behavior
The ExceptionsManager should log root exception cause here:
Here the root cause is pretty obvious for an experienced RN developer (the lib uses
React.PropTypes.bool
while this has been removed, and app startup crashes on JS load)This would be extremely useful to avoid loosing time debugging the root cause to log the stacktrace or the full error instead of just the
e.message
string.That would permit the developer to navigate easily through his Chrome developper tools to the root cause file.
Actual Behavior
The errors and stacktraces offered to the developer are very unhelpful, particularly for more complex cases where the message is not clear to understand what's happening.
Even in this case, I know perfectly what is happening, yet I have to debug to know which library does produce this behavior. I should just have to click on the stacktrace to get this information.
Reproducible Demo
I can add one if needed but honnestly I think this bug report is good enough to change
console.error(e.message)
toconsole.error(e)
:)Other
This issue has already been reported recently but closed: #16205
The text was updated successfully, but these errors were encountered: