RESOLVER_NOT_FOUND
What RESOLVER_NOT_FOUND means, why NotFoundError throws it, what to show users and how to fix it in ensforge. Also covers retry safety.
NotFoundErrorNot retryable
@ensforge/sdk
What happened
The name has no resolver.
What to show users
| Title | Message | Action |
|---|---|---|
| No resolver | This name is not set up to hold records yet. | Set a resolver first. |
How to fix
Set one with resolver.set.
Retry safety
Retrying the same call fails the same way until the cause is fixed (retryable: false).
Actions that throw it
| Action | When |
|---|---|
approval.getDelegate | when the name has no resolver. |
approval.setDelegate | when the name has no resolver. |
dns.setRecords | when the name has no resolver. |
permission.setRecordAccess | when the name has no resolver. |
record.get | with strict when the name has no resolver. |
record.getAddress | with strict. |
record.getAvatar | with strict. |
record.getContentHash | with strict. |
record.getText | with strict. |
record.set | when the name has no resolver of its own. |
resolver.get | with strict when nothing resolves the name. |
resolver.getLink | without a resolver, or with strict and no records. |
resolver.link | when the name has no resolver of its own. |
resolver.resolve | when nothing resolves the name. |
resolver.upgrade | when the name has no resolver of its own. |
role.get | when the name has no resolver. |
Catch it
Errors.hasCode("RESOLVER_NOT_FOUND") narrows to this error. See Handle errors.
Was this page helpful?