gnosis / safe-react Public
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
Fix: undefined address in reverse ENS lookup #3512
Conversation
|
CLA Assistant Lite All Contributors have signed the CLA. |
| owners | ||
| .filter(({ addressFieldName }) => !!formValues[addressFieldName]) | ||
| .map(async ({ addressFieldName }) => { | ||
| const address = formValues[addressFieldName] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The error on Sentry was coming from here. address was undefined somehow.
ESLint Summary View Full Report
Report generated by eslint-plus-action |
Pull Request Test Coverage Report for Build 1847477254
|
|
E2E Tests Failed Failed tests:
|
|
Looks good to me Names in an AB also loaded properly |


What it solves
Resolves #3507
How this PR fixes it
Just a quick fix that checks that the address isn't undefined.
I couldn't reproduce the error from Sentry. We actually don't allow empty addresses.
But this should fix it.
How to test it
Try creating a Safe with several owners, some of which are ENS owners.
The text was updated successfully, but these errors were encountered: