4.2.0-0.1.0 [Feature] Error Handling for UNSUPPORTED_CHAIN_MSG #186
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.
Description
This PR introduces an error message when bn-server sends back the
UNSUPPORTED_CHAIN_MSG
. The message is received when the requestednetworkId
is not allowed by the users tier. The websocket will close and an error message is returned (introduced in this PR https://github.com/blocknative/bn-server/pull/1273)This PR also moves the
simulation
error handling further down the file so that unhandled error messages do not get caught at an undefinedevent
object.Prior to this fix, the SDK will just fail here
With the fix, end users will see a user friendly error message.
Checklist
package.json
is incremented following semantic versioning