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

Add transaction_error_msg and send error to sentry #1752

Merged
merged 1 commit into from
Sep 25, 2020

Conversation

rickycodes
Copy link
Member

@rickycodes rickycodes commented Aug 6, 2020

previously we were showing the error to the end user for send/confirm transactions:

image

instead we now display a more generic error message and send the error to sentry.

there's a few other spots where we likely want to do the same thing:

here: https://github.com/MetaMask/metamask-mobile/blob/develop/app/components/Nav/Main/index.js#L764
here: https://github.com/MetaMask/metamask-mobile/blob/develop/app/components/Views/Approval/index.js#L209
here: https://github.com/MetaMask/metamask-mobile/blob/develop/app/components/Views/ApproveView/Approve/index.js#L666
and here: https://github.com/MetaMask/metamask-mobile/blob/develop/app/components/Views/SendFlow/Confirm/index.js#L801

we should probably update those as well.

@rickycodes rickycodes requested a review from a team as a code owner August 6, 2020 14:57
{ text: strings('navigation.ok') }
]);
error && Logger.error(error, 'error while trying to send transaction (Confirm)');
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what about having the error message still displayed to users? maybe that's valuable for cases like low gas or something

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think displaying the error might be useful, but we should be doing more than just displaying the issue? I'm honestly not sure what makes the most sense here. a failure could happen for any number of reason, so maybe a generic failure message isn't that useful? I think ultimately it should be a generic message with maybe an option to expand to show error details? idk 🤷‍♀️

@rickycodes rickycodes merged commit c451e17 into develop Sep 25, 2020
@rickycodes rickycodes deleted the feature/error-handling branch September 25, 2020 18:07
rickycodes added a commit that referenced this pull request Jan 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants