getMethodData() default to abi decoded method if registry lookup errors #6367
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This fixes a bug that was causing the confirm screen to navigate to the simple send confirm screen when it should have been navigating to the token transfer confirm screen. This could happen in when the http request made by "registry.lookup" failed.
Our router depends on the contract method name when the registry lookup failed, the name passed to the router was undefined.
This PR adds a fallback in our
getMethodData()
function - the use of abiDecoder.decodeMethod -which prevents the above described issue. W