grpc-ecosystem/grpc-gateway · error

no field %q found in %s

Error message

no field %q found in %s

What it means

Field-resolution error from Registry.resolveFieldPath: a component of the dotted field path does not match any field of the message currently being descended (lookupField returned nil). The error reports the whole requested path and the root message name; the faulting input is a misspelled or nonexistent field name in an HttpRule path/selector expression.

Source

Thrown at internal/descriptor/services.go:346

			f := result[i-1].Target
			switch f.GetType() {
			case descriptorpb.FieldDescriptorProto_TYPE_MESSAGE, descriptorpb.FieldDescriptorProto_TYPE_GROUP:
				var err error
				msg, err = r.LookupMsg(msg.FQMN(), f.GetTypeName())
				if err != nil {
					return nil, err
				}
			default:
				return nil, fmt.Errorf("not an aggregate type: %s in %s", f.GetName(), path)
			}
		}

		if grpclog.V(2) {
			grpclog.Infof("Lookup %s in %s", c, msg.FQMN())
		}
		f := lookupField(msg, c)
		if f == nil {
			return nil, fmt.Errorf("no field %q found in %s", path, root.GetName())
		}
		result = append(result, FieldPathComponent{Name: c, Target: f})
	}
	return result, nil
}

View on GitHub (pinned to a58a4436a3)

Solutions

1. Correct the field name spelling/casing in the HttpRule path template.
2. Regenerate descriptors so the message definition is current.
3. Confirm the field exists in the request message and is not filtered by registry config.

When it happens

Trigger: Thrown at internal/descriptor/services.go:346 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of grpc-ecosystem/grpc-gateway@a58a4436a3 (2026-09-02). Data as JSON: /api/errors/46e7bf27a410e9e2. Report an issue: GitHub.