GATEWAY_RESPONSE_INVALID
What GATEWAY_RESPONSE_INVALID means, why GatewayError throws it, what to show users and how to fix it in ensforge. Also covers retry safety.
GatewayErrorNot retryable
@ensforge/sdk
What happened
The off-chain gateway returned an invalid response.
What to show users
| Title | Message | Action |
|---|---|---|
| Lookup failed | The service that stores this name's data returned invalid data. |
Retry safety
Retrying the same call fails the same way until the cause is fixed (retryable: false).
Actions that throw it
| Action | When |
|---|---|
dns.claim | when the proof cannot be fetched. |
dns.getOffchainResolver | when the DNSSEC gateway fails. |
dns.getProof | when the DNSSEC gateway fails. |
dns.getStatus | when the DNSSEC gateway fails. |
primaryName.get | when an off-chain gateway fails. |
record.get | when an off-chain gateway fails. |
record.getAddress | when an off-chain gateway fails. |
record.getAvatar | with strict when NFT metadata cannot be loaded. |
record.getContentHash | when an off-chain gateway fails. |
record.getText | when an off-chain gateway fails. |
resolver.resolve | when an off-chain gateway fails. |
Catch it
Errors.hasCode("GATEWAY_RESPONSE_INVALID") narrows to this error. See Handle errors.
Was this page helpful?